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 220065 - After installation of full NetBeans (i.e. with Glassfish and Tomcat) only Glassfish appears under Services/Servers but not Tomcat
Summary: After installation of full NetBeans (i.e. with Glassfish and Tomcat) only Gla...
Status: RESOLVED WONTFIX
Alias: None
Product: ide
Classification: Unclassified
Component: Features On Demand (show other bugs)
Version: 7.3
Hardware: PC Mac OS X
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-14 11:38 UTC by host
Modified: 2014-12-11 10:48 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description host 2012-10-14 11:38:36 UTC 
I have downloaded the full version of NetBeans 7.3 daily - i.e. together with GlassFish 3.1.2 and Tomcat 7.0.32 - and (cleanly) installed this full package - i.e. in the installation dialogue I went to the advanced settings and also selected Tomcat along with the preselected Glassfish.

Now, when I open the Services tab and there the Servers, then I see only "GlassFish Server 3.1.2" registered but not Tomcat 7.0.32.

But well, I guess I know the reason: After activating "Java Web and EE" then the instance "Tomcat 7.0.32.0" actually also appears under servers.

So, this seems to be working as designed but it is counterintuitive for the novel user to see the JavaEE server GlassFish from the very start but (without any notice) Tomcat only after activating J2EE.

Actually, it would rather make sense from the user perspective that the Tomcat instance is shown from the very beginning and the "JavaEE and Web" stack is activated when first accessing the Tomcat server (properties).
Comment 1 Jaroslav Tulach 2012-10-22 09:21:54 UTC 
Is this a regression or a feature request? Did it ever work?
Comment 2 host 2012-10-22 09:25:11 UTC 
I guess this never worked as I would expect it. From my point of view, this would therefore be a bugfix but it could well be argued for to be an enhancement only.
Comment 3 Jaroslav Tulach 2014-12-11 10:48:45 UTC 
Anybody insists on this issue still be fixed?