[
https://issues.apache.org/jira/browse/CXF-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654250#action_12654250
]
Sergey Beryozkin commented on CXF-1929:
---------------------------------------
Thanks Freeman ! I didn't realize you were looking into it.
If you can get a chance, may be you can also do the same for 1.0 api ?
Actually, I'm wondering, would it make sense just to rename
trunk/jsr311-api-0.8
into
trunk/jsr311-api-1.0
and jsr311-api-1.0 specs bundle, given that it only contains a rewritten
FactoryFinder should be usable in cases when cxf 2.1.x which currently depends
on 0.8 api is used ?
> CXF-Bundle should include JSR311-API
> ------------------------------------
>
> Key: CXF-1929
> URL: https://issues.apache.org/jira/browse/CXF-1929
> Project: CXF
> Issue Type: Bug
> Components: OSGi, REST
> Affects Versions: 2.1.3
> Environment: OSGi, ServiceMix, Spring-DM
> Reporter: Hendy Irawan
> Assignee: Freeman Fang
>
> cxf-bundle does not include jsr311-api, and a OSGi-compatible jsr311-api
> bundle is not provided externally.
> This makes application developers have to embed jsr311-api inside application
> bundle JAR(s).
> Note that in my case, simply wrapping jsr311-api (0.8) and installing it
> (into ServiceMix kernel) doesn't work, throwing ClassNotFoundException in
> javax.ws.rs.core and org.apache.cxf.jaxrs.utils . Only embedding works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
