You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by nhrraj <ra...@gmail.com> on 2012/06/22 01:44:48 UTC
Exception when using jaxb-impl-2.2.4-1.jar with cxf 2.3.11
Hi,
I am migrating my jee server app to use cxf 2.3.11. App is installed in WAS
8.0.3
When initializing a webservice bean, I am getting the below exception.
Caused by: javax.xml.bind.JAXBException
- with linked exception:
[java.lang.reflect.InvocationTargetException]
at org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:577)
at
org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:410)
... 150 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:575)
... 151 more
Caused by: java.lang.ClassCastException:
com.aa.xxxx.xxxxwebservice.CheckLock$JaxbAccessorF_requestXml incompatible
with com.sun.xml.bind.v2.runtime.reflect.Accessor
at
com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.instanciate(OptimizedAccessorFactory.java:199)
at
com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:191)
When I remove the jaxb-impl-2.2.4-1.jar from my EAR, the error vanishes.
Can someone please suggest me the right solution for this problem?
thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/Exception-when-using-jaxb-impl-2-2-4-1-jar-with-cxf-2-3-11-tp5710127.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Exception when using jaxb-impl-2.2.4-1.jar with cxf 2.3.11
Posted by Mark Streit <mc...@gmail.com>.
Nhrraj
Have you looked at this link
http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere ?
.... for info about using alternative WS stacks like CXF and Metro within
Websphere app server. WAS 7/8 bundle the Axis2 stack along with other
potentially conflicting stuff like JAXB, XML, etc.
Might help.
Mark
On Jun 25, 2012 3:12 PM, "Daniel Kulp" <dk...@apache.org> wrote:
>
> Likely some sort of classloade hiearchy issue again. You could try
> popping
> that jar into the endorsed dir to see if that helps at all. If not, check
> the settings for parent first/last, etc.. to see if you can get the right
> version picked up.
>
> Dan
>
>
> On Thursday, June 21, 2012 04:44:48 PM nhrraj wrote:
> > Hi,
> >
> > I am migrating my jee server app to use cxf 2.3.11. App is installed in
> > WAS 8.0.3
> >
> > When initializing a webservice bean, I am getting the below exception.
> >
> > Caused by: javax.xml.bind.JAXBException
> > - with linked exception:
> > [java.lang.reflect.InvocationTargetException]
> > at
> > org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:577) at
> > org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:410)
> > ... 150 more
> > Caused by: java.lang.reflect.InvocationTargetException
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 60) at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> > pl.java:37) at java.lang.reflect.Method.invoke(Method.java:611)
> > at
> > org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:575) ... 151
> > more
> > Caused by: java.lang.ClassCastException:
> > com.aa.xxxx.xxxxwebservice.CheckLock$JaxbAccessorF_requestXml
> incompatible
> > with com.sun.xml.bind.v2.runtime.reflect.Accessor
> > at
> >
> com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.instancia
> > te(OptimizedAccessorFactory.java:199) at
> >
> com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(Optim
> > izedAccessorFactory.java:191)
> >
> >
> > When I remove the jaxb-impl-2.2.4-1.jar from my EAR, the error vanishes.
> >
> > Can someone please suggest me the right solution for this problem?
> >
> > thanks.
> >
> > --
> > View this message in context:
> >
> http://cxf.547215.n5.nabble.com/Exception-when-using-jaxb-impl-2-2-4-1-ja
> > r-with-cxf-2-3-11-tp5710127.html Sent from the cxf-user mailing list
> > archive at Nabble.com.
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
Re: Exception when using jaxb-impl-2.2.4-1.jar with cxf 2.3.11
Posted by Daniel Kulp <dk...@apache.org>.
Likely some sort of classloade hiearchy issue again. You could try popping
that jar into the endorsed dir to see if that helps at all. If not, check
the settings for parent first/last, etc.. to see if you can get the right
version picked up.
Dan
On Thursday, June 21, 2012 04:44:48 PM nhrraj wrote:
> Hi,
>
> I am migrating my jee server app to use cxf 2.3.11. App is installed in
> WAS 8.0.3
>
> When initializing a webservice bean, I am getting the below exception.
>
> Caused by: javax.xml.bind.JAXBException
> - with linked exception:
> [java.lang.reflect.InvocationTargetException]
> at
> org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:577) at
> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:410)
> ... 150 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 60) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> pl.java:37) at java.lang.reflect.Method.invoke(Method.java:611)
> at
> org.apache.cxf.jaxb.JAXBUtils.createRIContext(JAXBUtils.java:575) ... 151
> more
> Caused by: java.lang.ClassCastException:
> com.aa.xxxx.xxxxwebservice.CheckLock$JaxbAccessorF_requestXml incompatible
> with com.sun.xml.bind.v2.runtime.reflect.Accessor
> at
> com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.instancia
> te(OptimizedAccessorFactory.java:199) at
> com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(Optim
> izedAccessorFactory.java:191)
>
>
> When I remove the jaxb-impl-2.2.4-1.jar from my EAR, the error vanishes.
>
> Can someone please suggest me the right solution for this problem?
>
> thanks.
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Exception-when-using-jaxb-impl-2-2-4-1-ja
> r-with-cxf-2-3-11-tp5710127.html Sent from the cxf-user mailing list
> archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com