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 95631 - Runtime tab contents should indicate how an EJB or web module got deployed
Summary: Runtime tab contents should indicate how an EJB or web module got deployed
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-15 05:28 UTC by _ gsporar
Modified: 2007-02-15 09:37 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gsporar 2007-02-15 05:28:05 UTC
Composite Applications can use EJB and web applications.  Those EJB and web
applications can be deployed in one of two ways:

1. Directly to GlassFish.  In other words, right-click the EJB or web
application project and select Deploy.

2. As part of a JBI compliant Composite Application. In other words, right-click
the Composite Application and then add the EJB or web application to it as a JBI
Module.  Then Deploy the Composite Application.

That's all fine and well, but the IDE's GlassFish plugin does not distinguish
between the two techniques when it displays the GlassFish status over in the
Runtime tab.  When the list of EJB applications is shown they all look the same
- there is no distinction based on how they were deployed. The same is true for
web applications.

This seems like a problem because the application life cycle for an application
deployed directly as compared to an application deployed as part of a Composite
Application is very different.  Seems like it would be good to give the user
some visual markers to let them know which is which.  Please note that whatever
change is made, it should be coordinated with the GlassFish admin. console tools
folks.  They have the exact same problem today (and will hopefully repair it).