[shrinkwrap-issues] [JBoss JIRA] Commented: (SHRINKWRAP-242) Get shrinkwrap to work from inside and OSGi framework
[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
Andrew Rubinger commented on SHRINKWRAP-242:
--------------------------------------------
I haven't considered that, no.
What I'm thinking perhaps is a separate "ShrinkWrap Static
Initializer/Config" which can accept a CL, and then use that for all subsequent
static access. So if AS were to initialize for the user; no matter what API the user
called, the CL set through the initializer would be the one consulted.
WDYT? This is a prime reason why static access should be avoided, but ShrinkWrap is
intended to be EASY, and users love this aspect of the API. (I don't see many people
consulting the more manual routes that aren't static).
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