I noticed that between 1.24, and 1.25 isDeployable was changed to no longer allow META-INF as a path for sub deployable modules. The original code would only skip jboss-service.xml files in META-INF. Was this behavior change intended?
The reason I ask is because I was testing an application we are currently developing against the 3.2.x branch against 4, and one of the problems was that I had used META-INF/lib for nested jars. I am sure there are others that have used this convention. I wish the specification was more clear on this, because it seems that there is no "standard" way to handle nested jars. What should the correct behaivor of sub-deployments in ejb-jar files? Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849031#3849031 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849031 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
