[
https://issues.apache.org/jira/browse/FELIX-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091204#comment-17091204
]
Rakesh Kumar commented on FELIX-6267:
-------------------------------------
I made it work using framework property -
*org.osgi.framework.system.capabilities.extra = \*
*osgi.contract;osgi.contract=JavaJSONP;uses:="javax.json,javax.json.spi,javax.json.stream";version:List<Version>="1.1,1.0"*
In my case I am embedding Felix and the JSON-P(Glassfish RI) is on the
application classpath and the required *javax.json** packages are exported by
using
*org.osgi.framework.system.packages.extra* framework property.
This works fine and appears less intrusive, error prone to me (at least in my
case).
Please let me know if I continue with this approach or Sling commons json
Johnzon way is the preferred way here?
> Felix cm.json v1.0.2 could not start due to missing capability requirement
> (&(osgi.contract=JavaJSONP)(version=1.1.0))
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-6267
> URL: https://issues.apache.org/jira/browse/FELIX-6267
> Project: Felix
> Issue Type: Bug
> Reporter: Rakesh Kumar
> Priority: Major
>
> I have just upgraded to Felix cm.json to v1.0.2 and the bundle could not
> start due to newly introduced capability requirement.
> osgi.contract; (&(osgi.contract=JavaJSONP)(version=1.1.0))
>
> However, the bundle v1.0.0 was working without any issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
