[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
Andrew Rubinger commented on SHRINKWRAP-242:
--------------------------------------------
I don't mind things being involved in the SW side (in terms of changing the impl), but
our users rather like this syntax:
JavaArchive archive = ShrinkWrap.create(JavaArchive.class)
...requiring the CL to be passed in for things to work isn't likely to be embraced by
our users. Sure, we could add an additional method to accept the CL, but my feeling is
that folks won't use this option; then stuff will break when their archives get into
AS.
I'll find you on IRC to discuss further...both solutions look workable, and both also
look detrimental to overall user experience.
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