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: | Status of servers not displayed | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Ann Sunhachawee <asunhachawee> |
Component: | Tomcat | Assignee: | Petr Pisl <ppisl> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | ckutler |
Priority: | P3 | Keywords: | USABILITY |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ann Sunhachawee
2003-12-09 19:14:07 UTC
To accomodate this, an instance need to have attribute 'name' which is shorter than the URL and more user-friendly. This attribute is only used for displaying on the node and on the output tab; the URL is still the key for all instance references. It should be possible to solve this by custom nodes provided by plugins that would show shorter name and annotate it with status. There should be a consistent way -- Ann what should it be? Perhaps: http:/localhost:8080/ [running|stopped] I agree that showing status on node name should be server specific because for some server plugin implementation, pinging for status could result in bad responsiveness when expanding the parent node. Even with caching, first time pinging still slow. Should we change this issue to tomcatint's issue now that we have control from the plugin? Agreed, assigning to Petr P. This is doable by providing instance node from plugin, which will have this in the display name. Some further discussion is needed between Pavel B, Nam, Ludo and myself on this issue, so please hold off on the changes. The bundled servers should be consistent in how they show status, and this does not seem possible given Nam's comment. Is there any result how is should be done? For consistence across platforms, technically I think that we can do this at the j2eeserver level. j2eeserver ServerInstance currently has short-term cache of server status. The status is refreshed everytime we actually do the ping to the server. InstanceTargetXNode is refresh every time this status change. We can have it override display name from plugin not using InstanceProperties.DISPLAY_NAME_ATTR + <status>. Is non-realtime status acceptable, i.e., case users start/stop for outside IDE, the status will not change until the next time users do some activitity that would require a ping to the server? Another issue is if we go forward with this, should we replace start/stop with 2 separate actions? Fixed Verified. |