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

[ https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl... ] Andrew Rubinger commented on SHRINKWRAP-242: -------------------------------------------- OK, so I see what you've done here with the SWS. We're getting closer to meeting in the middle. Though this might not be necessary to have a separate SWS...instead of injecting Domain you could inject ArchiveFactory directly, which already has methods to mirror the static ShrinkWrap util. This is actually why I made Domains, ArchiveFactories etc in the first place; so we could inject under a specific config (and this config would not interfere with other configs in the VM). The only problem is that users would have to inject the ArchiveFactory as obtained from the, and any usage of ShrinkWrap utility methods would still be OSGi non-compatible. Does this solve the problem? Will be have cases of users STILL using ShrinkWrap.create() from within the OSGi environment? I think of course we will. So let's take the two-pronged approach: 1) Add to Domain/Configuration/ArchiveFactory a CL association to be used instead of TCCL. 2) Provide mechanism to apply a given CL for static usage (effectively configuring the default Domain/Configuration). The preferred usage inside AS will be to get an ArchiveFactory from MSC. Failing that, use the static thing, which we'll configure properly (though the timing issues you mention will be at play). Approve? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira