Changing the class loader policy to PARENT_LAST should resolve these issues.
It helped me fix these issues on WebSphere v8
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-in-deploying-cxf3-0-2-jar-in-Websphere-8-5-tp5751255p5753369.html
Sent from the cxf-dev mailing list
> On Jan 18, 2015, at 10:14 PM, Jason Pell wrote:
>
> Hi Dan,
>
> Any thoughts on timeline for next patch release?
Likely early Feb. We did the last set in early December so 8 weeks or so
would put it in early Feb.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Communi
Hi,
I guess the problem is that other neethi version (not 3.0.3) is loaded from
Websphere application server.
Could you please experiment with classloader options (try parent_last)?
This link could help a bit more:
http://stackoverflow.com/questions/17568330/incompatible-neethi-jar-with-was-7