This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Unlike the v2 plugin, the v3 plugin has no place to change the admin username or password. There is also no place to change the HTTP port. I tried changing the properties directly in the .netbeans\6.8m1\config\GlassFishEE6 and .netbeans\6.8m1 \config\J2EE\InstalledServers .nbattrs files, put they reset as soon as NB is restarted.
this is really an enhancement request, unless you can demonstrate a use case where the absence of the property blocks progress completely...
The standard Glassfish v3 installer (not packaged with NB) does not install a domain by default. Are users of the plugin supposed to know that the servers must use "admin" as the admin username and must use "adminadmin" as the password? If so, does that sound like a good security practice, even in a development or testing environment? I disagree with you Vince. I don't think this isn't a feature that needs added - this is something that is missing. My two cents of course... For a workaround, is there any way to just change the config files manually?
I guess I still do not understand your use-case, could you provide a step-by-step instructions that demonstrate a problem?
Use cases: 1. The server does not have a admin user named "admin" 2. The server has an admin user named "admin", but the password for that use is not "adminadmin"
and what is the problem that you encounter?
I cannot view any of the server nodes in the Services window for that server. I suspect the reason is that it uses a different admin username/password than the plugin's defaults. I would try to deploy an app to it, but I can't even select it as a server instance in the project properties. I assume the reason for that is because I haven't connected to that server yet. I am however able to select and view the default instance Netbeans installed on my machine.
Maybe something else is the matter... I reinstalled GF v3 b60 on my test server with the all the defaults: anonymous access, admin port 4848. I can't even connect to that with NB, even though I can access the admin console fine through the browser. I even tried a separate machine that runs nothing with no success. The only luck I've had with the v3 plugin and a remote domain is using localhost. Any thoughts / suggestions?
which build of NB 6.8 are you using? which os? can you provide detailed steps to specify what actions you are taking??? Have you deleted the NetBeans userdir?
I was using M1 on an XP machine, but when I deleted out the Netbeans folder, the Java Web and EE feature seemed to remove itself. Instead of messing around with it, I downloaded the latest nightly and I could connect fine. Now that I have a working plugin, I've been playing around with what works and what doesn't. I've found out that if the HTTP port of GF isn't set to 8080, then the plugin doesn't work. I do have to say that when it's working, the v3 plugin is much faster than v2 when working remotely - I'm looking forward to using it!
Tagging as 68cat
I still have to admit that I do not know what problems you are running into. I have asked you provide detailed steps to replicate the situation that you are in... Without detailed steps, I am at a bit lost on how to proceed.
As of the latest build, the following plugin parameters cannot be changed from their defaults: HTTP Port (default: 8080) Admin username (default: admin) Admin password (default: adminadmin) In addition, once the remote server URL and admin port are set they cannot be changed. If any of the server parameters ever change, the server has to be deleted out and added back in from scratch. Then if server name is off by so much as a character, the server has to be changed in each project. IMO, while this lack of configurability would have been sufficient for a beta plugin, the current plugin isn't production quality yet.
What problems are you running into that make you think that these parameters need to be configurable?
Let's approach this from another angle. I think you're saying the installer just put in the domain with the default user name, password, and port number and you'd like to change these. Wouldn't you just create a new domain from the command line for GF? Then you could add that domain no problem using the Add Server wizard.
While I have GF installed locally to give the plugin a runtime, I use a remote testing server for my integration / acceptance testing. Since I don't want just anyone logging into the admin console, I don't use the default username or password. With the Glassfish v2 plugin, I can change the username and password, but with the v3 plugin I can't. I have to change my v3 domain setup to accommodate the plugin, where I didn't have to with v2. Key question here: why is the GF v3 plugin not as functional as the GF v2 plugin? Likewise, I'm not sure I understand where NB is coming from on this one. All of the server properties are stored in a properties file in the .netbeans folder. It would seem that all is required to add the functionality are some extra form fields. With all the time that has been spent talking about it, this task could have been completed weeks ago.
In answer to your 'key question'... The v3 plugin is less functional because the functionality has not been demonstrated to be necessary when working with v3.
This is especially true when the remote domain has a password and custom port settings. Issue one: The IDE doesn't detect that the remote server is running... The tests to determine if the domain is running are targeting the http port (which the user does not enter) instead of the admin port... (which IS entered by the user). Issue two: the authentication does not get triggered correctly, so tests that determine if the server is running fail before the authentication dialog even has a chance to open. Issue three: even if the server is detected and an app deploys... the http port is not detected correctly... so the browser opens targeted at the WRONG port.
Integrated into 'main-golden', will be available in build *200909241442* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/796a3649ecdc User: vince kraemer <vkraemer@netbeans.org> Log: #170576: improve work-flow with remote custom domains... custom ports, authentication
in the nightly
Despite the fact that code was committed for this issue, the reasons for which this issue was opened have not be fixed, resolved or completely addressed. Whatever has been fixed or patched should have been covered under another issue.
Yes. the enhancement you originally requested has not been implemented. I fixed the issue that I encountered when I tried to duplicate your work-flow. I have changed the Summary back to the original value and re-marked the issue as an enhancement.
*** Bug 179758 has been marked as a duplicate of this bug. ***
*** Bug 181658 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 166648 ***