.
Best regards
Stephan
From: cschneider...@gmail.com [mailto:cschneider...@gmail.com] On Behalf Of
user-return-18355-stephan.siano=sap@karaf.apache.org
Sent: Mittwoch, 21. März 2018 18:35
To: user@karaf.apache.org
Subject: Re: Karaf 4.2.0M2 issue with classpath
If you have control over that code
If you have control over that code then the TCCL is a good solution.
Christian
2018-03-21 16:54 GMT+01:00 bobanbp :
> Hi Christian,
>
> Thanks for your reply. I tried your suggestion but without success. The
> only
> solution that works is to explicitly change class loader:
>
> ClassLoader tccl
Hi Christian,
Thanks for your reply. I tried your suggestion but without success. The only
solution that works is to explicitly change class loader:
ClassLoader tccl = Thread.currentThread() .getContextClassLoader();
Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
Hi Boban,
I guess the AWS SDK is not importing these packages so they are not
visible.
Of course it can not really import the packages as it does not know what is
behind the API.
There is one thing you can try though. Add the com.ctc.wstx.* packages to
org.osgi.framework.bootdelegation in config.
I'm migrating our application to the newer version of Karaf and I started
testing our application on karaf 4.2.0M2. Before 4.2.0M2 I performed some
tests on Karaf 4.1.4 and it worked fine, but on 4.2.0M2 I hit an issue. I am
getting the flowing error:
javax.xml.stream.XMLInputFactory: Provider
com
