Yes .. your problem with the starting state might be a CXF problem.
I think I had a similar problem with the launcher basically I needed to
start the at leastr one CXF top level bundle by hand.
I am not sure how to solve this though. Maybe you can also ask in the
bndtools user list how to handle such case. We might need to fix it in CXF
but I am not sure about how to approach it.
Christian
On 08.12.2015 23:15, matteo wrote:
Hi Christian,
Thank you for the response. Yes, the bnd-maven-plugin will help a lot and
I'm really looking forward its release. But in this case I'm not sure the
problem is due to some missing dependencies.
I saw your comments to CXF-6687
<https://issues.apache.org/jira/browse/CXF-6687> : you mentioned it was a
problem in the Karaf launcher but you also said that you were able to
reproduce the issue when trying CXF with bndtools. What was your impression
in this case? A similar problem in the aQute.launcher.Launcher?
The STARTING description in OGSi says that /If the bundle has a lazy
activation policy, then the bundle may remain in this state for some time
until the activation is triggered./ /Triggered/ seems a synonym of /first
class load from the bundle occurs/: probably the blueprint endpoint
configuration I'm using does not trigger the the cxf bundles activation?
matteo
-----
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-3-1-4-bundles-remain-in-starting-state-tp5763687p5763731.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
