I couldn't give you an answer to this without looking at use cases. I would certainly stick to the current rules (deepest first).
My gut fealing is that you pass each deployment/subdeployment individually down the chain. i.e. assume each deployment is independent. PRO: We don't want subdeployments manipulating each other's data, they should refer to each other via by reference/dependency CON: If they are truly independent why would they be packaged together, so maybe there are usecases where this tighter coupling is desirable? Remember, when I talk about coupling I am talking about the metadata processing. They will of course be tightly coupled by the microcontainer when they are constructed and wired together from the metadata. The use case I can think of where coupling of metadata is required is when the classloader metadata is constructed. Each subdeployment can add metadata (urls) to the top level metadata that creates the classloader. This is probably the more common pattern. i.e. Each subdeployment builds up metadata (e.g. urls) at the top level which is processed last and adds global policy (e.g. classloader isolation, java2 delegation, etc.) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863421#3863421 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863421 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
