On the server side. If you can point me to any information about replacing the engine it will be very helpful. Thanks.
-----Original Message----- From: Johan Edstrom [mailto:[email protected]] Sent: Sunday, January 27, 2013 10:48 AM To: [email protected] Subject: Re: Reuse JAXB context in jaxws In a client or in the server? On a server you can easily replace the whole engine. On Jan 27, 2013, at 1:37 AM, Avner Levy <[email protected]> wrote: > In the past I've posted a question about reusing jaxb context between > services. > Daniel Kulp suggested configure a data binding object in the following form > (for the specific scenario): > > <jaxws:endpoint xmlns:tns="urn:ihe:iti:xcpd:2009" .......> > <jaxws:dataBinding> > <bean class="org.apache.cxf.jaxb.JAXBDataBinding" > > <constructor-arg index="0" ref="globalJAXBContextBean"/> > </bean> > </jaxws:dataBinding> > > I've tried to do the same through code: > > > jaxwsEndpoint.getProperties().put("org.apache.cxf.jaxb.JAXBDataBinding", > jaxbDataBinding); before calling: > jaxwsEndpoint.publish(URL); > > And the service starts very fast as if they are reusing the context in the > jaxbDataBinding object passed. > But when connecting later I've discovered that the service context contains > only 50 classes while the original contained 700. > Any idea how come I finish with a different context? > Thanks in advance, > Avner > Email secured by Check Point
