Hi, I have a jar file, lets call it ejb.jar, that contains both the interface and implementation of several stateless session beans. I typically deploy ejb.jar and one other jar containing stateless session beans in an ear. I am now working on a sar file that contains a single MBean, this MBean makes use of some of the stateless session beans in the ejb.jar. The sar that deploys my MBean can't be bundled in the ear with ejb.jar because it has to be flexible so that it can use the stateless session beans locally or talk to them remotely if they are deployed in a separate JBoss instance.
Since the sar may be running on a separate machine, it at least needs to have the interfaces for my EJBs on the classpath, so it has ejb.jar in the root of the sar. My problem is that when trying to deploy the sar, JBoss wants to deploy the EJBs also but fails because there is no persistence unit definition (it's usually found in the ear's META-INF). So is there a way to tell JBoss not to deploy the stateless session beans that it is finding in the sar? If not then I guess my next alternative would be to deploy this as a war, but that's not ideal in this case. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266401#4266401 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266401 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
