No, you didn't miss anything. It is purposely vague being that every app server has different operational requirements for a target environment. In some ways, you are seeing a bi-product of JBoss's deployment process in handling something like this.
Deployment of a ResourceAdapter in JBoss is a bit confusing. 1) RAR is deployed to deploy directory 2) RAR properties are applied and the ResourceAdapter created. 3) *After* this you use a *-service.xml file to populate and bind the AdminObject into JNDI, set values etc, etc. Not something I am thrilled with actually and I am debating ways to make this more accesible, or at the very least, more intuitve to understand. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955900#3955900 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955900 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user