[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
David Bosschaert commented on SHRINKWRAP-242:
---------------------------------------------
From what I can see it looks good, but there are some sections in the
changes that I'm not too familiar with :)
So just to make sure, let's say I have the following use case.
I want to create an ArchiveFactory that uses ClassLoader clA for loading the
shrinkwrap-impl-base module, what would the code look like?
Also, is there ever a case where more than 1 module needs to be visibile by the
classloader? I mean maybe the shrinkwrap-impl-base module and one or more additional
modules? If this is ever the case it would be worth considering allowing a collection of
classloaders to be specified...
Get shrinkwrap to work from inside an OSGi framework
----------------------------------------------------
Key: SHRINKWRAP-242
URL:
https://issues.jboss.org/browse/SHRINKWRAP-242
Project: ShrinkWrap
Issue Type: Task
Affects Versions: 1.0.0-alpha-11
Reporter: David Bosschaert
Assignee: David Bosschaert
Priority: Critical
Fix For: 1.0.0-beta-1
Currently there are issues around the use of Shrinkwrap in an OSGi framework. The
libraries don't contain the necessary Manifest headers and just adding them causes
classloading problems as the TCCL is used during the boot process.
Shrinkwrap should be usable from within OSGi.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira