anonymous wrote : I'd like to see the classloaders constructed like other beans:...
It might be possible to support this level of configuration, but in general there needs to be an abreviated form that builds the class loader hierarchy based on some associated model (current flat repository model, hiearchical repository model, standard parent child model, ...) since as we know, users having to deal with the type system/ packaging/redeployment/class loader interaction details is not one of the favorite jboss user expierences. I'm expecting that this is what is encapsulated in the "convenience configurations". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863602#3863602 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863602 ------------------------------------------------------- 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
