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.
Summary: | [65cat] registered servers are not shown when creating new "Enterprise Application" project | ||
---|---|---|---|
Product: | javaee | Reporter: | kretes <kretes> |
Component: | Code | Assignee: | Petr Hejl <phejl> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | vkraemer |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
kretes
2008-10-08 14:28:16 UTC
checked only with glassfish v3 prelude b28 Only servers that supports the selected type of projects (technology) are visible. Could You tell more about that? Isn't glassfish an JEE 5 server that should allow 'enterprise application' project? Even if no - this is confusing if the wizard let me add a server, show me the list, I add the server, and after that - there is no server to be chosen ( you say no 'supported' server ) - there should be some info about that. I understand that glassfish v3 is for some (?) reason not a EJB container but web container. The same would be for Tomcat which is also on server list. However - it is still confusing. - The server creation wizard should indicate which server is of what type - there should be a decoration near the server name or some label that would say which server is pure web container , which is JEE (preferably even with the spec version supported ), or any other environment ( if server in NB can be of other type as well, don't know if servers for other purposes like Ruby or php are in the same bucket as well. This is definitely not a P1 defect. Trouble is that is certain cases you can't say the server capabilities until it is registered. hmm ok, I didn't know that, this looks more complicated than I thought - I thought it is known at the moment of creating a server plugin. Anyway - I'm fine with that. *** This bug has been marked as a duplicate of bug 156116 *** |