First, I'm not especially tied to the DomainClassLoader. The main thing I need is a notion of dynamic package availabilty so the bean or deployment can say:
| <demand type="package">org.jboss.xxx</demand> | | it could also be specialized as | | <requires-packages>org.jboss.xxx,org.jboss.yyy</requires-packages> | Then the bean is not attempted to be described (class analysed) until the package(s) is deployed. I achieved this in the prototype by making the classloader architecture register itself as KernelRegistryFactory for dependency checking. NOTE: The explicity demand is only intended for classes unknown to the BeanMetaData. i.e. it should be done automatically for the package of the bean class, etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867938#3867938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867938 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
