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 56987

Summary:	Runtime tree doesn't refresh when the resource is registered
Product:	serverplugins	Reporter:	Alexander Kouznetsov <mrkam>
Component:	GlassFish	Assignee:	Nitya Doraisamy <nityad>
Status:	NEW ---
Severity:	blocker	CC:	pjiricka, vkraemer
Priority:	P3
Version:	4.x
Hardware:	PC
OS:	Windows ME/2000
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Alexander Kouznetsov 2005-03-25 13:07:11 UTC

Steps to reproduce
- Start App Server 8.1 
- In Runtime tab expand Runtime > Servers > Sun Java System Application Server 8.1 > JDBC > Connection Pools nodes
- Register non-registered JDBC Connection Pool (create it if neccessary). It will be successfully registered.
RESULT: Open Runtime tab again and verify that connection pool isn't added here yet. To see it you should refresh the node. 

The same situation is for the JDBC Resources and Persistence Resources.

Comment 1 Nitya Doraisamy 2005-03-31 18:19:31 UTC

Deploy project action and the register action on resource should follow up with
a call to refresh the runtime area in order for the latest server snapshot to be
displayed.

Comment 2 pcmreddy 2005-04-06 17:46:34 UTC

This bug fix is requested by JSE team. Exceptions needs to be handled properly.
Marking this bug as P1

Comment 3 pcmreddy 2005-04-06 17:51:08 UTC

This functionality is needed for coming JSE release.

Comment 4 _ ludo 2005-04-06 17:55:50 UTC

P3 bug. There is a workaround, to call refresh manually.

Comment 5 _ ludo 2005-04-14 12:23:52 UTC

We cannot find a fix other than maybe completely refreshing the entire tree and
that could be another p3 bug in itsef...
The main issue is that there is no notification back from the runtime of
changes...The model is really handled by the backend server (because apps or
resources could be also deployed outside the IDE)...That's why we have this
refresh action, to resynchronize the IDE with the current state of the server.
If the node has not been explored previously, then you'll have the correct value
since to improve perf, we do lazy loadind on the necessary data for each node.

Comment 6 Nitya Doraisamy 2005-04-15 17:23:10 UTC

The runtime tree is not connected to the activity in the projects tab. So no
refresh is initiated after a deploy or register. Initiating an overrall refresh
will result in the entire tree being refreshed, as Ludo described. This needs to
be looked into to see if it is possible to refresh only the set of affected
runtime components. ie. say web project is deployed, the web modules node and
aoociated resoures nodes will need to be refreshed.

Comment 7 Vince Kraemer 2006-01-04 18:39:44 UTC

*** Issue 61200 has been marked as a duplicate of this issue. ***

Comment 8 Vince Kraemer 2008-04-25 17:47:16 UTC

should we add this to the 6.5 task list for the v3 plugin? bonus points if it ends up working in the v2 plugin... but
not a requirement.

Comment 9 Vince Kraemer 2008-10-17 23:20:23 UTC

I guess we need to resolve this issue in 7.0.

Please be ready to discuss this on 2008/10/22.

Comment 10 Vince Kraemer 2009-12-10 12:54:58 UTC

no bug should be assigned to issues. distributing the load.