cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andriy Redko (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-7045) Update sample description_swagger2_osgi README.txt
Date Fri, 16 Sep 2016 16:23:20 GMT

    [ https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496718#comment-15496718
] 

Andriy Redko edited comment on CXF-7045 at 9/16/16 4:22 PM:
------------------------------------------------------------

Hi Sergey,

I think it is feasible in general, but why would CXF provide a feature to install just Jackson?
Here is basically the concern I have. F.e. if I am building an application and I need to install
additional bundles (Jackson is good example, like you mentioned), I do know that and I will
install them. Now, it happens that our own sample project has to include some additional bundles
as well. We could make this process easier (by pre-installing some bundles, hopefully users
will need them anyway) or ask user to do that. 

I am honestly not sure about having dedicated CXF feature for Jackson, it feels like that
should not be the CXF responsibility but Jackson itself. However we do have similar use cases,
f.e. *cxf-jaxb*, so I think in general it might be OK. So it would mean to have standalone
*cxf-jackson* feature, and *cxf-rt-rs-service-description-swagger* will depend on it as well,
right?

Thanks.

Best Regards,
    Andriy Redko 


was (Author: reta):
Hi Sergey,

I think it is feasible in general, but why would CXF provide a feature to install just Jackson?
Here is basically the concern I have. F.e. if I am building an application and I need to install
additional bundles (Jackson is good example, like you mentioned), I do know that and I will
install them. Now, it happens that our own sample project has to include some additional bundles
as well. We could make this process easier (by pre-installing some bundles, hopefully users
will need them anyway) or ask user to do that. 

I am honestly not sure about having dedicated CXF feature for Jackson, it feels like that
should not be the CXF responsibility but Jackson itself. However we do have similar use cases,
f.e. cxf-jaxb, so I think in general it might be OK. So it would mean to have standalone *cxf_jackson*
feature, and *cxf-rt-rs-service-description-swagger* will depend on it as well, right?

Thanks.

Best Regards,
    Andriy Redko 

> Update sample description_swagger2_osgi README.txt
> --------------------------------------------------
>
>                 Key: CXF-7045
>                 URL: https://issues.apache.org/jira/browse/CXF-7045
>             Project: CXF
>          Issue Type: Bug
>          Components: Samples
>            Reporter: John Poth
>            Assignee: Freeman Fang
>            Priority: Minor
>             Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve org.apache.cxf.samples.jax_rs_description_swagger2_osgi
[146](R 146.0): missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
[146](R 146.0)] osgi.wiring.package; (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
Unresolved requirements: [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R
146.0)] osgi.wiring.package; (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message