You're going the wrong way about it -- the idea is that the beans use the java:comp/env/jdbc/bps lookup name that is mapped to the app server's environment (arbitrary datasource name).
You don't need to change your datasource configuration or jndi-name, what you want to do is configure jboss.xml for your beans that maps the java:comp/env/jdbc/bps lookup to the datasource JNDI name binding (these are defined in the standard EJB xml as resource reference entries and then mapped in jboss.xml to app server's datasource deployments). It's not a bug, it's a case of misunderstanding/abusing the spec provided mechanisms. Introductory guides books on J2EE using JBoss as example deployment environment will give you more details. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012106#4012106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012106 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
