Has anyone tried to intregate Tomcat and Jboss lately? Here are the instructions from contrib, I am wondering if they are still up to date. Step 2 talks about deleting parser.jar. It doesn't say where but neither tomcat 4.0b4ish or jboss 2.3ish have a parser.jar that I can find. That makes the renaming crimson.jar to parser.jar sound fishy too. Anyone know the reasoning behind step 2? 1) copy embedded.jar to jboss/lib/ext, tools.jar should go to that directory too (or included in CLASSPATH) 2) copy the files jaxp.jar (from catalina_home/server) to jboss/lib, delete parser.jar, copy crimson.jar (from catalina_home/server) to jboss/lib/parser.jar 3) add the following lines to jboss.conf changing the directories accordingly <MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar" CODEBASE="../../lib/ext/"> <ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-4.0-b1/server/"> </MLET> <MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar" CODEBASE="../../lib/ext/"> <ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-4.0-b1/lib/"> </MLET> <MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar" CODEBASE="../../lib/ext/"> <ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-4.0-b1/bin/"> </MLET> 4) there are 3 mbeans that need to be configured in jboss.jcml: the EmbeddedManager to launch EmbeddedCatalina <mbean code="org.apache.catalina.startup.EmbeddedManager" name="Catalina:name=Catalina"> <attribute name="UseNaming">false</attribute> </mbean> the mbean that will configure EmbeddedCatalina according to server.xml configuration <mbean code="org.jboss.contrib.catalina.ConfigCatalinaService" name="Catalina:name=Config"> <attribute name="ServerXmlPath">../../jakarta-tomcat-4.0-b1/conf/server.xml</attribute> <attribute name="CatalinaHome">../../jakarta-tomcat-4.0-b1/</attribute> <attribute name="DeployHostname">localhost</attribute> </mbean> and the deployer <mbean code="org.jboss.deployment.J2eeDeployer" name="J2EE:service=J2eeDeployer"> <attribute name="DeployerName">Default</attribute> <attribute name="JarDeployerName">:service=ContainerFactory</attribute> <attribute name="WarDeployerName">Catalina:name=Config</attribute> </mbean> 5) start jboss, all war files will be deployed to localhost as configured in ConfigCatalinaService. To see the typcal home page http://localhost:8080 enable the root context in server.xml. limitations: Realm and Resources not yet integrated. Tomcat naming disabled _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user