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.
It looks like a the strategy for naming a connection pool (and other resources???) in ResourceConfigurator.java may make it easy to end up overwriting data that should not be shared between deployed applications. See: http://javacollassato.wordpress.com/2008/06/15/multiple-enterprise-application-and-jpa-does-not-work-in-netbeans-61/
I believe this is a non-issue. To solve the problem described in the URL, just be sure to to change your “sun-resources.xml” file under “Server Resources” in NetBeans the following way: <jdbc-resource enabled=”true” jndi-name=”MY_JNDI_NAME” object-type=”user” pool-name=”MY_POOL_NAME”/> <jdbc-connection-pool … name=”MY_POOL_NAME” … > … This way, Glassfish will automatically create your JDBC pool upon deployment.
Actually, it is a bug in our code. The fact that you can work-around it is what makes it a p3 bug, not a p1 or p2 bug. The plugin wrote the initial data that triggered the issue.... and it was pretty easy to identify what was "wrong"...
please fix this for 6.5.
would embedding the jndi name of the jdbc resource that this pool is being created to be associated with solve the issue? It looks like it will. See ResourceConfigurator.java in the method createDataSource....
Embedding the jdbc resource name would work but will result in multiple connection pools for the same db. The plugin creates a poolname using the database vendor name(eg.derby_net) and the checks to make sure that a similar pool is not present in the project. But a second project using Derby for a JDBC resource will result in the same connection pool name (derby_net). A good strategy would be to use a longer name say, dbvendor+dbname+user. I think this would cover 95+% of the cases
Integrated into 'main-golden', available in build *200808010201* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/9b3d40ea3d0a User: nityad@netbeans.org Log: #137837 : Fix for weak naming strategy in creating connection pools pool names now use vendor + dbname + user add dependency on glassfish.eecommon from appsrv to for v2 plugin to reuse url parsing logic
Plugin now uses vendor_dbname_user_Pool to generate unique name for connection pools
Integrated into 'main-golden', available in build *200808210201* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/46789c081002 User: nityad@netbeans.org Log: #137837 : Fix for weak naming strategy in creating connection pools pool names now use vendor + dbname + user