[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
David Bosschaert commented on SHRINKWRAP-242:
---------------------------------------------
Yeah - I think that would work.
You'd really want to use the injected version though - so we should extend Arquillian
to inject that into test cases. It's quite tricky to otherwise find out what the
classloader is that loads the impl module/bundle which you have to pass to the CL-extended
methods. I mean how would you do this reliably? Iterate over all the modules you know
until you find the right one? Which one is the right one (in case there is more than one
version of this thing available)?
This is where the service-based approach comes in handy. The *impl* bundle can create an
instance and register it with MSC. It knows its own classloader. Then nobody else needs to
know that information and it works reliably.
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