Here is my web.xml <servlet>
<servlet-name>XFireServlet</servlet-name> <servlet-class> org.codehaus.xfire.transport.http.XFireConfigurableServlet </servlet-class> </servlet> Here is my services.xml <beans xmlns="http://xfire.codehaus.org/config/1.0";> <bean name="jaxbServiceFactory" class="org.codehaus.xfire.jaxb2.JaxbServiceFactory"> <constructor-arg ref="xfire.transportManager" /> </bean> <service> <name>AutoTerritoryService</name> <!-- bean defined in applicationContext.xml --> <serviceBean>#autoTerritoryServiceImpl</serviceBean> <serviceFactory>#jaxbServiceFactory</serviceFactory> <style>document</style> <use>literal</use> <scope>application</scope> </service> </beans> -----Original Message----- From: Dragos Pavel [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 12:49 PM To: [email protected] Subject: RE: [xfire-user] XFire / JAXB Rook You said you are using JAXB2 bindings. Can you be more precise about that switch: because in web.xml you can have XFireConfigurableServlet: <servlet- class>org.codehaus.xfire.transport.http.XFireConfigurableServlet</servle t-class> but in services.xml you must have JaxbServiceFactory: <serviceFactory> org.codehaus.xfire.jaxb2.JaxbServiceFactory </serviceFactory> if you said you are using JAXB2 bindings right ? If you change the factory in the services.xml then you are not using JAXB2 anymore , correct me if I'm wrong please. On Thu, 2007-17-05 at 11:22 -0500, Bradford, Jeff L wrote: > Switched back to the XFireConfigurableServlet instead of the > XFireSpringServlet, using services.xml. Now working. > > -----Original Message----- > From: Dragos Pavel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 16, 2007 7:24 PM > To: [email protected] > Subject: Re: [xfire-user] XFire / JAXB Rook > > > Yes, I am experiencing this (2 imports of XSD or 2 schema in the > generated wsdl) since 9 days now. > > Same thing was happening to me, calling the service with a client, when > was arriving in the IMPL class the req object did not had the right data > and couldn't be deserialised based on the wrong schema from the > generated wsdl. > > Because of this issue I am trying to implement a workaround to use the > original wsdl instead of the generated one. I just discovered (yes, read > again the manual...) that to do so we have to intermix the Spring and > XFire syntax by using the XBean. > > Here is a link for a must read: > http://xfire.codehaus.org/Spring%2C+XBean%2C+Servlets+and+more > > Signed, > YouAreNotTheOnlyDesperado > > > On Wed, 2007-16-05 at 17:23 -0500, Bradford, Jeff L wrote: > > XFire - 1.2.2 > > JAXB > > Spring > > XFireSpringServlet > > > > Writing first web service. Did contract first development and used > > XFire to gen my server stubs. > > > > Implemented my business logic and modified the IMPL class. > > > > Business logic works fine, having trouble wiring the service. > > > > The service is deployed to JBoss locally. It is able to respond to > > the request to display the WSDL file via the browser. The wsdl file > > does have 2 imports of XSD files. > > > > When I call the service with a client or via SoapUI, when it arrives > > in the IMPL class the req object is blank. > > > > I have been stuck for days on this issue and can not figure out why > > this is happening. Has anyone experienced something similar when you > > were a rook? > > > > Please help. > > > > > > Signed, > > Desperado > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
