NB 6.0 20070619 & GF v2 b50c

With a web project:

** add a JMS resource QueueConnectionFactory keep the default jndi name
jms/myQueue

** add a JMS resource admin-obj Queue keep the default jndi name
same default value as proposed previously.

==>> jndi name is not uniq 
Before the wizard uses digit myQueue_1, myQueue_2 each time called now is no more the case

** deploy the application ==>> error of deployment as expected.
but the connectionFactory is deployed

** update the sun-resources.xml file to have:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Resource Definitions //EN"
"http://www.sun.com/software/appserver/dtds/sun-resources_1_3.dtd">
<resources>
  <admin-object-resource enabled="true" jndi-name="jms/myQueue" object-type="user" res-adapter="jmsra"
res-type="javax.jms.Queue">
    <description/>
    <property name="Name" value="nana"/>
  </admin-object-resource>
  <connector-resource enabled="true" jndi-name="jms/myQueue" object-type="user" pool-name="jms/myQueue">
    <description/>
  </connector-resource>
  <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0"
connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory"
connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false"
idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false"
lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32"
max-wait-time-in-millis="60000" name="jms/myQueue" pool-resize-quantity="2" resource-adapter-name="jmsra"
steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
</resources>

jndi-name changed to jms/myQueueFact connector-resource

** undeploy & deploy the project ==>> error
** try to delete the jms/myQueue Connector Resources with IDE action "Services/Connectors/Delete"
==>> error.

** only way to remove the resources from the domain.xml file
and to restart the instance.