[
https://issues.jboss.org/browse/SHRINKWRAP-242?page=com.atlassian.jira.pl...
]
David Bosschaert commented on SHRINKWRAP-242:
---------------------------------------------
Right - so I can see that for OSGi, this static initializer would be set by the
shrinkwrap-impl-base bundle once it becomes active. However, there are timing issues with
this approach. What happens if the consumer uses SW before it was initialized?
That's where the service-based approach that I used earlier is nice because it's
the *impl* bundle that registers the service. The service registry caters for handling the
dependencies and effectively it won't be possible to even find SW in that case before
its initialized. The disadvantage of the service base approach is clearly that it requires
a service registry of some sort (e.g. jboss-msc, OSGi services or even JNDI).
So yeah I can see that users love the static approach, but we need to find an easy
solution that ensures that initialization has happened before any invocation is done...
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