The downside is that (in the hypothetical example) you can only override config exposed by EJBDeployment whereas the plain BeanMetaData configs expose everything for configuration.
But this could be worked around by allowing an "advanced config option" List beans = EJBDeployment.getBeans(); //process beans to add config; EJBDeployment.setBeans(beans); Although that is probably too simplistic to scale across multiple separation of concerns and would be brittle to internal changes within the EJB metadata model. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863607#3863607 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863607 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
