Hi, > -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory while > starting the weblogic server solves the issue.
OK, EclipseLink JAXB context implementation was used instead Sun one and it causes the problem by CXF. > Now the question is how can I make sure that application uses sun's > implementation. > Is there any bean configuration in jaxws? > or adding jaxb.properties in domain classes? > > still failing to load if server does not have the sun's implementation in java > options. > please suggest is there a way to ask WL server to use the sun's jaxb > implementation Not sure is there better solution as configuring -Djavax.xml.bind.JAXBContext JVM option in your Application Server. @Dan: could you suggest any other options here? Regards, Andrei. > -----Original Message----- > From: chandramohan [mailto:[email protected]] > Sent: Dienstag, 30. April 2013 13:04 > To: [email protected] > Subject: RE: CXF webservice applocation failing on weblogic12c Cluster > > I found a quick fix. > By passing a java option as > -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory while > starting the weblogic server solves the issue. > > that means if not defined CXF uses JAXBContext as > org.eclipse.persistence.jaxb.JAXBContextFactory. > > Now the question is how can I make sure that application uses sun's > implementation. > Is there any bean configuration in jaxws? > or adding jaxb.properties in domain classes? > > still failing to load if server does not have the sun's implementation in java > options. > please suggest is there a way to ask WL server to use the sun's jaxb > implementation > > Thanks, > Chandramohan > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/CXF- > webservice-application-failing-on-weblogic12c-Cluster- > tp5726535p5726956.html > Sent from the cxf-user mailing list archive at Nabble.com.
