We don't use EAR deployment or EJBs but we did have a number of war files that worked fine under a standalone Tomcat installation. These war's required specific version of some classes.
To support this I changed a configuration attribute for the whole JBoss Tomcat installation that made it work more like a standalone version. We've not experienced any problems from do thing. I suspect it may not be making best use of the class repository. For JBoss 3.2.2: In jbossweb-tomcat41.sar/META-INF directory fine the jboss-service.xml attribute. Add/change mbean attribute: false By default it is true. Hope this helps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841347#3841347 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841347 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
