The points you mention are clear more less, i.e. deployers don't know their next, they all process the deployment after the structure has been identified and they don't instantiate objects directly. Their order is decided at registration time.
What I'm trying to understant is, when having a deployment with nested subdeployments, if it is important for any given Deployer to process the deployment & subdeployments completely (either parent first, or depth first), before the next in the chain does the same. (This was the first scenario described) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863411#3863411 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863411 ------------------------------------------------------- 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
