[
https://issues.apache.org/jira/browse/DELTASPIKE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556300#comment-14556300
]
Harald Wellmann commented on DELTASPIKE-905:
--------------------------------------------
{{java.util.ServiceLoader}} does not really work well in OSGi in general. See
http://aries.apache.org/modules/spi-fly.html.
I know it's a more general issue, but so far I only had to fix it in this one
place, presumably because in all other use cases I've tested in the context of
DeltaSpike data, the TCCL just happens to be suitable.
The question is how much OSGi-awareness (in terms of compile-time or run-time
dependencies) is acceptable for DeltaSpike - this will determine the approach
to a more generic solution.
> Missing OSGi headers in Proxy modules
> -------------------------------------
>
> Key: DELTASPIKE-905
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
> Project: DeltaSpike
> Issue Type: Bug
> Components: PartialBean
> Affects Versions: 1.4.0
> Reporter: Harald Wellmann
> Fix For: 1.4.1
>
>
> {{deltaspike-partial-bean-module-impl}} imports package
> {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing
> OSGi manifest headers.
> This breaks Partial Beans and Data modules for OSGi users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
