We need a lot more information. Are you using Aegis on both ends? We've probably got incompatibilities there. Your best bet would be to get a WSDL out of the service and run wsdl2java, and then use JAX-B on the client.
On Mon, Jan 17, 2011 at 1:38 PM, seydi moha <[email protected]> wrote: > > Hello, > > I have a problem with my service. > My server is on xFire and my Client application on cxf. When i try to contact > my service, my interceptor is ok, but my client object populate null; > I think that the problem came from xfire Soap response not recognize by Cxf > client. > I need a help please to debug this. > > Thanks. > > Sorry i have a bad english. > > > --------------------------- > ID: 1 > Address: https://...../MyService > Encoding: UTF-8 > Content-Type: text/xml > Headers: {SOAPAction=[""], Accept=[*/*]} > Payload: 168C3754-800E-FE4F-3160-C8E0B593CE2C > -------------------------------------- > 17 janv. 2011 19:23:59 org.apache.cxf.interceptor.LoggingInInterceptor logging > INFO: Inbound Message > ---------------------------- > ID: 1 > Response-Code: 200 > Encoding: ISO-8859-1 > Content-Type: utf-8 > Headers: {connection=[Keep-Alive], Keep-Alive=[timeout=15, max=100], > Date=[Mon, > 17 Jan 2011 18:24:22 GMT], transfer-encoding=[chunked], Server=[Apache], > content-type=[utf-8]} > Payload: SESS-494EE635-B90B-5589-71B0-6A0E8BCF7C40 > -------------------------------------- > [INFO] webservices.WebServicesUsed sessionID : > null--------------------------------------------------------------------------------- > > Best Regards, > > To contribute to the environmental protection, thank you for printing > this e-mail only in case of necessity > --------------------------------------------------------------------------------- > > Best Regards, > > To contribute to the environmental protection, thank you for printing > this e-mail only in case of necessity > > > >
