I'm looking into ways of solving this. The idea for a parent module won't solve all problems, I think.
For example consider: deploy/test-service.xml deploy/management/test-service.xml You get the same problem, but there is certainly no notion of an enclosing parent module here. For the way jboss works, the absolute deployment url is the ultimate id for a deployment, so my idea would be to add it in the name, e.g. jboss.management.local:J2EEServer=Local,j2eeType=ServiceModule,name=iiop-service.xml url=file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.4.GA/server/all/deploy/iiop-service.xml View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939830#3939830 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939830 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
