I can currently think of two solutions. (1) Still put all ESB examples in the same domain as RiftSaw, with parent being DefaultDomain and perhaps parent-first=true
Don't see why this would be a problem? Or why would you need multiple domains? Their parent is DefaultDomain, hence they see all what default stuff sees. (2) Be "OSGi" exact Split / extract the conflicting jar into separate deployment, and give it proper jboss-classloading.xml e.g. readable module name + *proper* version Do the same with its updated version. Then simply reference the right exact module, whereas you don't need to define any separate domains. It's definitely more work, plus you need to wrap existing external jars, but this is a known OSGi issue - see SS's huge effort of creating proper repository. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250131#4250131 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250131 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
