1. Install a build from the installer, including the bundled servers (GF v2 and v3 Prelude)
2. Start this build with a fresh userdir
3. Go to Services tab - there is no Servers node. I expect to see the Servers node with the bundled servers registered
The workaround is to create a new web project, which will make the Servers node visible, but this workaround is not
Reproduced using build 200903311400.
Servers node in now visible. Still that is not enough. We also need to make sure all the installed servers are visible
under that node.
Created attachment 79396 [details]
Petře H. what do you think could the RootNode enable enterprise cluster when expanded and there are some servers?
> Servers node in now visible.
I don't see it in the latest build, presumably this change is not propagated yet. Are you referring to this change?
I must say I don't think that's the right approach, because this will mean that the Servers node is visible also in the
C++, PHP and JavaSE distribution, which is not desirable. It should only be visible in All, Java and Ruby - same as in 6.5.
*** Issue 161698 has been marked as a duplicate of this issue. ***
Created attachment 79528 [details]
Real patch with fix, test and usage of the API in JavaEE cluster.
Petr, can you please review and integrate my patch? Also there seems to be some problem with listening to list of
installed servers. As soon as I expand the node, the Java EE functionality is enabled, but no Tomcat or Glassfish V2
is visible. I need to right click on the node and choose Add Server. Then the list of installed servers refreshes. Can
you please fix this refresh problem and then mark this as fixed? Thanks.
Hi. It looks like this commit http://hg.netbeans.org/main-golden/rev/149aa862edd5 is a partial attempt to resolve this
Is that commit going to get rolled back, once this issue is resolved completely?
It seems like it is the root cause of issue 162063 and issue 162064.
*** Issue 162063 has been marked as a duplicate of this issue. ***
Just downloaded M3 and found the Servers node missing. I think this is really confusing, a poor design, and will require
multiple emails/service calls on the users alias. It's certainly breaks the seamless experience between GlassFish and
Fixed in web-main 877170f42056.
Jardo perhaps the action should go to j2eeserver or similar place (it is strange that there is tomcat related property
mentioned in layer of glassfish)?
I tried the build that contains the fix, and the behavior is still really broken. I filed issues 162273, 162274 and
162275 against the current behavior:
I guess that now, when we have three issues instead of one, we can close the original.
Integrated into 'main-golden', will be available in build *200904091401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #161664 Installed Servers must be visible by default
I found one additional minor UI problem, which I filed as issue 162768.