[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
David Bosschaert commented on SHRINKWRAP-242:
---------------------------------------------
There has been an email thread in relation to this in the mean time. You can see the
thread here:
http://lists.jboss.org/pipermail/jboss-as7-dev/2010-December/000125.html
I think we can take 2 routes on this
1. We can take the route that I took above which is around getting the existing SW to
work. It has the disadvantage in that it turns it into a service which does a bit of magic
around setting of the TCCL when its being invoked. It has minimal impact on SW itself. The
disadvantage is that the service needs to be obtained and that the whole setup feels a
little bit like a workaround...
2. Or... we can take the route that Thomas suggests in the email mentioned above. This
would mean that SW is used as a utility class using simple static methods. It would mean
that its reliance on the TCCL needs to be factored out. In order to make it work with
module systems it needs classloaders as arguments to its methods instead. This is
definitely a nicer solution, but it's more involved on the SW side...
Get shrinkwrap to work from inside and 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