Hi Matt,
Ah ok, I got it. It's probably a race condition, as the wrap deployer
would need some time to wrap on the fly the jar as bundles. However, the
wrap deployer should "lock" the jar to avoid to process it again in
cycle. Let me check if we changed something there.
Regards
JB
On 01/28/2016 07:24 PM, goku3989 wrote:
Hi JB,
I do have a similar exception about javax.annotation (complaining about
com.fasterxml.jackson.core.jackson-databind) but that actually gets reported
after the exception about jackson-datatype-joda-2.6.2.jar that I had listed
below.
The JARs I need are seemingly all there in the deploy directory, but a bunch
of them don't have the compliant OSGi manifests. It seems like it's trying
to load JARs before the dependency JARs have been wrapped. Once the wrap
deployer does its thing, it seems like everything is able to start, but I
have to explicitly stop the container and then restart it. With 3.0.3, with
the exact same JARs in deploy, I didn't need to do the explicit restart.
Thanks for your help,
-Matt
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-4-Bundle-exception-Unresolved-requirement-on-first-startup-tp4045034p4045050.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
