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 75037 - Disable and Enable of deployed applications does not function after disabling an app from the Glassfish Admin Console
Summary: Disable and Enable of deployed applications does not function after disabling...
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-13 22:52 UTC by matthieu
Modified: 2006-07-27 06:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
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 matthieu 2006-04-13 22:52:50 UTC 
Running Glassfish 9.0-b41 and Netbeans 5.5 Dev 200604120200.

Enable and Disable from the Runtime tab in the IDE works fine and the status of
the applications change within the Glassfish Admin Console. If the Glassfish
Admin Console is used to change the state of an application then Netbeans does
not notice the change and can no longer make changes. Yet the Disable/Enable
menu option still changes in Netbeans. Once the application is re-enabled in
Glassfish's Admin Console then Netbeans can enable or disable the application again.
Comment 1 Sherold Dev 2006-04-14 08:14:05 UTC 
-> sunappserv
Comment 2 Nitya Doraisamy 2006-05-11 15:59:29 UTC 
Did you do a refresh on the glassfish runtime node after you changed settings
via the admin console? The runtime node does not refresh dynamically. I will
test this out too.
Comment 3 Nitya Doraisamy 2006-05-11 18:48:20 UTC 
The enable/disable viewed through the IDE is put of sync with the admin comsole
settings. Setting via IDE propagates but not from admin console. Runtime should
always reflect uptodate view of the server.
Comment 4 Nitya Doraisamy 2006-07-27 06:07:36 UTC 
There are two locations(<applications>, <servers>) within the domain.xml where
there is an enable flag for a deployed app and they may not in sync at any point
after the server starts. Admin console edits one(<servers>), though it uses the
both to indicate the status of the module. The plugin uses the other flag
(<applications>) to indicate status. 
Updated plugin to edit both locations and use both to indicate module's status.