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 175351 - most resource changes are ignored when saved
Summary: most resource changes are ignored when saved
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-24 01:18 UTC by Vince Kraemer
Modified: 2009-11-05 10:14 UTC (History)
1 user (show)

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 Vince Kraemer 2009-10-24 01:18:18 UTC 
It looks like apps are being redeployed when the sun-resources.xml file is changed, but most of the changes do not end
up in the server.

Steps to reproduce

build a recent pull of web-main
start the ide
activate the web and java ee features
install/register build 69 (I used the download now feature)
create a web app that targets the freshly registered server
deploy the web app
create a JDBC resource in the web app with a connection pool via the JDBC Resource wizard
verify that the resources were registered.
open the sun-resources.xml file
change the value of the User property from app to apple and save the change.
  you will see a message that the app is being deployed... but watch carefully 'cause if is speedy quick.
Open the properties dialog for the connection pool from the services explorer...
   Hmm. the User property still has the value app.

If you change the name attribute of the connection pool or the jndi-name of the jdbc-resource, the updates seem to stick.
Comment 1 Vince Kraemer 2009-10-24 01:23:52 UTC 
If I turn off deploy on save for the web app, before the first deploy, using the Run item after created the
jdbc-resource/connection-pool does not push the resource to server.
Comment 2 Nitya Doraisamy 2009-10-24 03:35:24 UTC 
The first issue is because the v3 resource registration does not update existing resources.
Changing the jndi-name or name (respectively) results in a new resource with the provided jndi-name/name being created.

V3 plugin resource registration will need to be changed to allow for updating an existing resource on deploy.

The second scenario,  Run on project with n additional newly created resource does not register the resource.
Investigating ...
Comment 3 Nitya Doraisamy 2009-11-04 18:44:06 UTC 
Fixed,
http://hg.netbeans.org/web-main/rev/b73b359ddba5
Comment 4 Quality Engineering 2009-11-05 10:14:00 UTC 
Integrated into 'main-golden', will be available in build *200911050201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/b73b359ddba5
User: nityad@netbeans.org
Log: #175351 : Fix for most resource changes being ignored on redeploy