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.

Bug 108171

Summary: Default server is not being picked up
Product: javaee Reporter: Lukas Jungmann <jungi>
Component: Web ProjectAssignee: Radko Najman <rnajman>
Status: VERIFIED DUPLICATE    
Severity: blocker CC: sherold
Priority: P2 Keywords: REGRESSION, T9Y, TEST, USABILITY
Version: 6.x   
Hardware: All   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Lukas Jungmann 2007-06-26 15:34:45 UTC
current trunk

-run IDE with clean userdir
-register some server (eg. glassfish) in the IDE (or use -J-Dcom.sun.aas.installRoot=/path/to/glassfish for IDE startup)
-open some web project received via email or checked out from VCS (= project is without private folder)

Expected: I'm able to run project without explicitly setting the target server for the project (IDE will choose the one
already registered for me automatically)

Current: I have to resolve missing server manually myself
Comment 1 Radko Najman 2007-06-27 16:49:47 UTC
It sounds to me much more as an enhancement that a defect. It wouldn't say it ever worked by this way so why a regression?

The project support was design to inform the user that server reference is broken and allow him to solve it, not to
automatically set the server if the problem appears.
Comment 2 Lukas Jungmann 2007-06-27 17:05:48 UTC
It worked as I described in 5.5, 5.5.1 and around 6.0 M9, therefore it is a regression. Or maybe a bug in older releases?

AFAIK resolve missing server dialog was shown only if there were > 1 instances of servers of particular type, but I can
be wrong with the condition...
Comment 3 Radko Najman 2007-06-27 17:09:39 UTC
Interesting, there are features which I don't know, I'm still learning new things :-)
Comment 4 Lukas Jungmann 2007-07-02 16:14:33 UTC
I've just discussed this with Stepan and the problem is caused by the change in the GF plugin. It have to be (and
already was) fixed in tests => marking this issue INVALID
Comment 5 Lukas Jungmann 2007-07-10 19:20:30 UTC
This is still valid :( It can be only workarounded by resolving missing server in tests => reopening....
Comment 6 Lukas Jungmann 2007-07-10 19:21:37 UTC
and marking as a dup of issue 108830, which is about the same thing

*** This issue has been marked as a duplicate of 108830 ***
Comment 7 Lukas Jungmann 2007-08-24 14:02:23 UTC
v.