[
https://issues.apache.org/jira/browse/CXF-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xilai Dai updated CXF-6687:
---------------------------
Description:
>From cxf 3.1.4, most of the bundles with setting lazy activation in the
>MANIFEST
{code}
Bundle-ActivationPolicy = lazy
{code}
This works well for Export-packages, but not work for Export-Service.
{code}
103 | Starting | 40 | 3.1.4 | Apache CXF Runtime JAX-RS
Frontend
104 | Active | 40 | 3.1.4 | Apache CXF Runtime Management
105 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Client
106 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Extensions:
Providers
107 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Extensions:
Search
108 | Starting | 40 | 3.1.4 | Apache CXF RS XML Security
109 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Service
Description
110 | Starting | 40 | 3.1.4 | Apache CXF Runtime Security
functionality
{code}
For example, when deploy a customer application with jaxrs:server in the
blueprint.xml, then it is waiting for namespace handlers
[http://cxf.apache.org/blueprint/jaxrs] until failed to start.
was:
>From cxf 3.1.3, most of the bundles with setting lazy activation in the
>MANIFEST
{code}
Bundle-ActivationPolicy = lazy
{code}
This works well for Export-packages, but not work for Export-Service.
{code}
103 | Starting | 40 | 3.1.4 | Apache CXF Runtime JAX-RS
Frontend
104 | Active | 40 | 3.1.4 | Apache CXF Runtime Management
105 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Client
106 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Extensions:
Providers
107 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Extensions:
Search
108 | Starting | 40 | 3.1.4 | Apache CXF RS XML Security
109 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Service
Description
110 | Starting | 40 | 3.1.4 | Apache CXF Runtime Security
functionality
{code}
For example, when deploy a customer application with jaxrs:server in the
blueprint.xml, then it is waiting for namespace handlers
[http://cxf.apache.org/blueprint/jaxrs] until failed to start.
> Some of the cxf bundles failed to export its OSGi service from CXF 3.1.4
> ------------------------------------------------------------------------
>
> Key: CXF-6687
> URL: https://issues.apache.org/jira/browse/CXF-6687
> Project: CXF
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 3.1.4
> Reporter: Xilai Dai
> Assignee: Christian Schneider
>
> From cxf 3.1.4, most of the bundles with setting lazy activation in the
> MANIFEST
> {code}
> Bundle-ActivationPolicy = lazy
> {code}
> This works well for Export-packages, but not work for Export-Service.
> {code}
> 103 | Starting | 40 | 3.1.4 | Apache CXF Runtime JAX-RS
> Frontend
> 104 | Active | 40 | 3.1.4 | Apache CXF Runtime Management
> 105 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Client
> 106 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS
> Extensions: Providers
> 107 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS
> Extensions: Search
> 108 | Starting | 40 | 3.1.4 | Apache CXF RS XML Security
> 109 | Starting | 40 | 3.1.4 | Apache CXF JAX-RS Service
> Description
> 110 | Starting | 40 | 3.1.4 | Apache CXF Runtime Security
> functionality
> {code}
> For example, when deploy a customer application with jaxrs:server in the
> blueprint.xml, then it is waiting for namespace handlers
> [http://cxf.apache.org/blueprint/jaxrs] until failed to start.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
