That is one way to implement it. It does have the advantage the deployers become simple and it would be easier for other deployers to pluck out the parts they want to work on.
e.g. A hypothetical deployer that wants to post process all EJB containers can do it more easily if it is looking for "metadata instanceof EJBDeployment" rather than a BeanMetaData with an open ended set of possibities like bean="StatelessContainer" or bean="CMPContainer" I don't understsand your second question. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863605#3863605 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863605 ------------------------------------------------------- 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
