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.
Shouldn't there be a warning instead of the exception. ...or even better, it would be good if the Server-Manager window pops up automatically if no valid server is there. java.lang.IllegalStateException at org.netbeans.modules.j2ee.deployment.impl.Server.getDisconnectedDeploymentManager(Server.java:141) at org.netbeans.modules.j2ee.deployment.impl.Server.getDisconnectedDeploymentManager(Server.java:132) at org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.getDeploymentConfiguration(ConfigSupportImpl.java:287) at org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.getWebContextRoot(ConfigSupportImpl.java:191) at org.netbeans.modules.web.project.ProjectWebModule.getContextPath(ProjectWebModule.java:93) at org.netbeans.modules.web.project.ui.customizer.WebProjectProperties.init(WebProjectProperties.java:326) at org.netbeans.modules.web.project.ui.customizer.WebProjectProperties.<init>(WebProjectProperties.java:260) at org.netbeans.modules.web.project.WebProject.getWebProjectProperties(WebProject.java:412) at org.netbeans.modules.web.project.WebProject$ProjectOpenedHookImpl.projectOpened(WebProject.java:706) at org.netbeans.spi.project.ui.ProjectOpenedHook$1.projectOpened(ProjectOpenedHook.java:50) at org.netbeans.modules.project.ui.OpenProjectList.notifyOpened(OpenProjectList.java:417) at org.netbeans.modules.project.ui.OpenProjectList.open(OpenProjectList.java:171) at org.netbeans.modules.project.ui.OpenProjectList.open(OpenProjectList.java:135) [catch] at org.netbeans.modules.project.ui.actions.NewProject$2.run(NewProject.java:145) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: The Application Server installation directory is not correctly set up. (Use the Tools>Options>IDE Configuration menu enter a correct value.) at org.netbeans.modules.j2ee.sun.ide.Installer$FacadeDeploymentFactory.getDisconnectedDeploymentManager(Installer.java:201) at org.netbeans.modules.j2ee.deployment.impl.Server.getDisconnectedDeploymentManager(Server.java:139) ... 20 more
High visible issue, I'm changing priority to P2.
Please, fix the issue in Beta release.
Due this issue user can't work with samples projects without installed Sun App server.
The app server is correctly sendin an exception: throw new DeploymentManagerCreationException(NbBundle.getMessage(PluginProperties.class, "MSG_WrongInstallDir")); when there is valid deployment manager (connected or not) So the caller (i.e j2eeserver plugin) has to nicely recover from this state. Not by dumping the stack trace... Ludo
This happens not only the blueprints solutions catalog but also other regular sample projects, i.e. web application. 1. install appserver 2. projectize web app 3. remove appserver 4. close the projectized web app Then you see the same exception. So I suppose this bug should be fixed on the higher level of j2ee project management.
The exception is caught and handled in a polite way now. User can continue in his work. The informational message will be, however, still printed in the log. Decrease priority from P1 to P3 Checking in src/org/netbeans/modules/j2ee/deployment/config/ConfigSupportImpl.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/config/ConfigSupportImpl.java,v <-- ConfigSupportImpl.java new revision: 1.42; previous revision: 1.41 done Checking in src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProvider.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProvider.java,v <-- J2eeModuleProvider.java new revision: 1.50; previous revision: 1.49 done Checking in src/org/netbeans/modules/j2ee/deployment/impl/Server.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/Server.java,v <-- Server.java new revision: 1.35; previous revision: 1.34 done Checking in src/org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java,v <-- ServerInstance.java new revision: 1.63; previous revision: 1.62 done Checking in src/org/netbeans/modules/j2ee/deployment/impl/ui/RegistryNodeProvider.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/ui/RegistryNodeProvider.java,v <-- RegistryNodeProvider.java new revision: 1.15; previous revision: 1.14 done
*** Issue 64743 has been marked as a duplicate of this issue. ***
Ludo, I have fixed the impact of this issue, so that only an information message is printed in the log now. We should, however, fix also the cause, which is an assumption of the j2eeserver that you can always create an instance of disconnected deployment manager from the url that the plugin provides through the netbeans-deployment file. See serverplugins/sun/appsrv81/src/org/netbeans/modules/j2ee/sun/ide/j2ee/nbdep.xml <disconnected-string>deployer:Sun:AppServer::localhost:4849</disconnected-string> Is the appserver plugin able to fulfill this contract, in case that the installation directory has not been set yet? If not, I will probably have to hide the informational message.
chicken and egg problem. We register via static layer file (for optimal start up time) the factory. But this factory can return as expected exception in case off missing server. We could add the entry in the layer file dynamically only when the server is there, but this would not solve the issue that sometimes it is valid to throw an exception at DM creation (the spec allows that)...
I don't think the j2eeserver is listening to netbeans-deployment file changes and thus the dynamic registration will most likely not work. Hiding the informational message is also not an option here, since the DeploymentManagerCreationException might also mean other problems that we should know about. I spoke with QE and everybody agrees that the fix should be now done in the blueprint sample projects. Wizard should offer a combo box with all registered servers and it should not be possible to finish the wizard unless a valid server is selected. This is most likely not doable for 5.0 Reassigning to j2ee/blueprints
*** Issue 64814 has been marked as a duplicate of this issue. ***
*** Issue 56134 has been marked as a duplicate of this issue. ***
*** Issue 65067 has been marked as a duplicate of this issue. ***
as of 051122 build, this is not reproducable.
QE confirmed that this is indeed fixed - marking as FIXED. Thanks.
[build 20051122] User doesn't get exception and resolve server dialog is opened. New Sun App server instance can be added here.
*** Issue 63038 has been marked as a duplicate of this issue. ***