[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: Running a GlassFish-developed-application on JBoss 4.2.2

[nitros]

I think the problem is with the two files admin-ds.xml and
transactions-ds.xml.  JBoss do not understand them.  Merge their
contents into one file called mysql-ds.xml and place it in the deploy
folder.  You should be able to hot deploy it and you will also see
JBoss binding to the JNDI name .  Moreover if you are using a default
installation of JBoss then you need another DS called DefaultDS for
JBoss to created JMS queues.  I suggest creating one more DS under the
JNDI name DefaultDS and pointing to one of your DB.

Check the file attached which is an example of my env.


       <local-tx-datasource>
               <jndi-name>EswaadAppDS</jndi-name>
...
               <valid-connection-checker-class-name>
                       org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
               </valid-connection-checker-class-name>
               <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
               
                       <type-mapping>mySQL</type-mapping>
               
       <!--  <security-domain>MySqlDbRealm</security-domain> -->
       </local-tx-datasource>

       <local-tx-datasource>
               <jndi-name>EswaadGlobalDS</jndi-name>
...
               <valid-connection-checker-class-name>
                       org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
               </valid-connection-checker-class-name>
               <exception-sorter-class-name>
                       org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
               </exception-sorter-class-name>
               
                       <type-mapping>mySQL</type-mapping>
               
       </local-tx-datasource>

       <local-tx-datasource>
               <jndi-name>DefaultDS</jndi-name>
...
               <valid-connection-checker-class-name>
                       org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
               </valid-connection-checker-class-name>
               <exception-sorter-class-name>
                       org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
               </exception-sorter-class-name>
               
                       <type-mapping>mySQL</type-mapping>
               
       </local-tx-datasource>



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133641#4133641

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133641