[shrinkwrap-issues] [JBoss JIRA] Issue Comment Edited: (SHRINKWRAP-242) Get shrinkwrap to work from inside an OSGi framework

[ https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl... ] David Bosschaert edited comment on SHRINKWRAP-242 at 3/30/11 4:13 AM: ---------------------------------------------------------------------- Just thinking a little more about the OSGi and JBoss-modules use-cases... While all of the above seems fine - there is a missing part IMHO. If you're in OSGi or in JBoss modules, it's still kinda hard to find out what the classloader is that you need to pass in. In the simple case its the classloader that loads the sw-impl-base module but how you find that classloader is non-trivial (I think). Therefore I would recommend that in addition to what you did, you register the ArchiveFactory as a service, either in MSC, in OSGi, or in both. This means that someone who wants to use SW from such an environment doesn't need to do any crazy stuff to find the appropriate classloader. The ArchiveFactory instance is just there. It also means that the user doesn't need to declare a hard dependency on the impl-base module. You can do this in a way that doesn't hamper anyone else... * For OSGi you simply add a bundle activator that registers the instance * For JBoss-modules/msc you add a service activator that registers the instance Ideally you would do both :) The nice thing is that if you're running outside of any of these the activators are ignored... If you need any help with this I would be happy to assist... was (Author: bosschaert): Just thinking a little more about the OSGi and JBoss-modules use-cases... While all of the above seems fine - there is a missing part IMHO. If you're in OSGi or in JBoss modules, it's still kinda hard to find out what the classloader is that you need to pass in. In the simple case its the classloader that loads the sw-impl-base module but how you find that classloader is non-trivial (I think). Therefore I would recommend that in addition to what you did, you register the ArchiveFactory as a service, either in MSC, in OSGi, or in both. This means that someone who wants to use SW from such an environment doesn't need to do any crazy stuff to find the appropriate classloader. The ArchiveFactory instance is just there. It also means that the user doesn't need to declare a hard dependency on the impl-base module. You can do this in a way that doesn't hamper anyone else... * For OSGi you simply add a bundle activator that registers the instance * For JBoss-modules/msc you add a service activator Ideally you would do both :) The nice thing is that if you're running outside of any of these the activators are ignored... If you need any help with this I would be happy to assist... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira