Thanks Peter! I used what you posted as starting point. Then, because we also require a clustered JMS set up i had to work back from an "all" config. Then because the developers need jmx-console access i had to add in JbossWS!
So, i wound up with: deploy: cluster/ deploy.last/ hdscanner-jboss-beans.xml jboss-local-jdbc.rar jbossweb.sar/ jboss-xa-jdbc.rar jca-jboss-beans.xml jms-ra.rar jmx-console.war/ jmx-invoker-service.xml jmx-remoting.sar legacy-invokers-service.xml messaging/ mysql-ds.xml properties-service.xml remoting-jboss-beans.xml security/ snmp-adaptor.sar sqlexception-service.xml transaction-jboss-beans.xml transaction-service.xml vfs-jboss-beans.xml deployers: ejb3.deployer/ jboss-aop-jboss5.deployer/ jboss-jca.deployer/ jbossweb.deployer/ messaging-definitions-jboss-beans.xml metadata-deployer-jboss-beans.xml security-deployer-jboss-beans.xml Now I'm CERTAIN i still have too much due to the JBossWS need (could not get it to start without ejb3.deployer). My guess is now i need to look into what services are getting called via the xml files. But in production i wouldn't have JBossWS anyway for the JMS solution. But this has been helpful and your info gave the me what i needed to get to this stage! Thanks so much! August View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247134#4247134 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247134 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
