[
https://issues.apache.org/jira/browse/FELIX-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091183#comment-17091183
]
Rakesh Kumar edited comment on FELIX-6267 at 4/24/20, 4:47 AM:
---------------------------------------------------------------
Looked into Sling
[https://github.com/apache/sling-org-apache-sling-commons-johnzon] and the
required capability is exported from the bundle itself.
Is that the preferred way, don't we have any existing bundle which provide this
capability? What I meant here is the JSON-P implementation having this header
exposed.
Just exploring options here.
was (Author: rakeshk15):
Looked into Sling
[https://github.com/apache/sling-org-apache-sling-commons-johnzon] and the
required capability is exported from the bundle itself.
Is that the preferred way, don't we have any existing bundle which provide this
capability?
> 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)
