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 173216 - Run Target does not call redepoy for new added resouce element
Summary: Run Target does not call redepoy for new added resouce element
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
: 173144 (view as bug list)
Depends on: 141982
Blocks:
  Show dependency tree
 
Reported: 2009-09-29 00:05 UTC by davisn
Modified: 2009-10-23 23:35 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 davisn 2009-09-29 00:05:34 UTC 
After run a web project, I add a new resource component to the project -> rerun the project, then the new added
component does not get deploy 

Step To Reproduce:
1. Install NB Trunk 09/22/2009 build
2. Create a web app
3. Select to run the project
3. Add to a web app a new JMS resouce (eg, use the default and name the JNDI as Testjms/myQueue
4. Go to Server -> GlassFish V3 Domain -> Resources -> Connectors node to view if "Testjms/myQueue" deployed.
BUG:
   Testjms/myQueue does not get deployed. It seems the run target does not know if there a new added element in the
sun-resources.xml file so it call invoke the re-deploy target before run
   If I add a new JSP or Servlet file to the project then the redeploy action was happening
Comment 1 Vince Kraemer 2009-09-29 02:12:42 UTC 
this seems like it is a dup of OR a variation of issue 173144
Comment 2 Vince Kraemer 2009-09-29 02:36:09 UTC 
see also issue 141982
Comment 3 Nitya Doraisamy 2009-09-29 02:41:09 UTC 
*** Issue 173144 has been marked as a duplicate of this issue. ***
Comment 4 Nitya Doraisamy 2009-09-29 02:44:05 UTC 
Right, issue 141982 does describe what triggers this issue. Basically, when the content of the setup/sun-resource.xml
file is modified, the changes are not detected and a redeploy operation is not triggered.

Investigating to see if 'Run' action can cause resource registration always.
Comment 5 Nitya Doraisamy 2009-10-23 23:35:30 UTC 
Fixed by changes for 141982