The second stage deployers still need to ordered, but it may not be the same order as the structural orders.
The difference is that ALL second stage deployers get to process the deployment. The second stage deployers create the BeanMetaData and (un)install it to the kernel. They DO NOT create objects explicitly, except where it would make no difference to dependency ordering. e.g. There is little point telling the BeanMetaData to instantatiate a java.lang.Integer through metadata when you can just pass the object directly as the value (this assumes you have the object already rather than just a string). So the ordering is less important at the second stage and only becomes relevent when one deployer wants to process metadata created by a previous deployer. This response is a repeat of a discussion we had at the end of last year. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863399#3863399 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863399 ------------------------------------------------------- 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
