"jaikiran" wrote : Can you give us more details about how your MDBs are packaged and where have you created the queue?
Certainly. What we have is (fairly) straighforward - a jobcontrol.ear file that contains the following: foo.jar - The core classes of our app. jobcontrol-ws.war - A web service interface for our app. jobcontrol-mdb.jar - The MDB that acts as an interface between the web service and the core classes. It responds to messages posted by the web service. At present jobcontrol-ws.war and jobcontrol-mdb.jar have some classes in common, which are themselves in common with the classes of foo.jar. This is not optimal but shouldn't be affecting our deployment right now, as far as I know. The EAR file also contains a bunch of libraries in jars, and the container on the server has a bunch more in its lib/ directory. None of these overlap, as far as I know. foo.jar, jobcontrol-ws.war, and jobcontrol-mdb do not have any libraries in them. The queue is created by the app server - the configuration in the EJB creates it, as can be seen at http://pastie.caboo.se/40508. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017033#4017033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017033 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
