Hello 

Well I'm using cxf on client side, the "Eclipse XML deserializer" is on the
server side (WebSphere Process Server) and fails because a
"ClassNotFoundException: Class 'pago' ". So I do connect cxf with this issue
because cxf is serializing and the deserialization is failing.  

//this is how I'm creating the client and invoking the service 
DynamicClientFactory dcf = DynamicClientFactory.newInstance(); 
Client client = dcf.createClient(url); 
client.invoke(operationName, pago); 

I’m not trying to say that cxf has a problem is just not working for me
perhaps one of you can tell me that I’m doing something wrong. Maybe I said
in the wrong way, actually cxf doesn’t fail but the server is rejecting the
xml on the parsing process

If I use different clients it works. Probably I'm doing something wrong Has
any one used cxf as a client of WebSphere services?

I’m attaching the wsdl with all the dependences 

Has any one used cxf as client to consume services running on WebSphere
Process Server?

Thanks in advance




bimargulies wrote:
> 
> I don't understand how you are connecting a class-not-found in an
> Eclipse XML deserializer with CXF. I don't see any CXF here at all. If
> you would be so kind as to post a JIRA showing CXF failing ... Also, I
> can't help wondering if this is rpc/encoded.
> 
> 
> On Sat, Aug 22, 2009 at 2:13 PM, Juan David<[email protected]> wrote:
>>
>> Hi All
>>
>> I’m trying to consume a web service that is running on WebSphere Process
>> Server. The client sends the request and the server replyes with a
>> general
>> exception when I check the server log I found that is rejecting the
>> request
>> when the server is processing the xml:
>>
>> Caused by: org.eclipse.emf.ecore.xmi.ClassNotFoundException: Class 'pago'
>> not found.
>>        at
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.validateCreateObjectFromFactory(XMLHandler.java:1999)
>>        at
>> com.ibm.ws.bo.bomodel.util.BOXMLHandler.validateCreateObjectFromFactory(BOXMLHandler.java:1296)
>>
>> I set up the tcp/ip monitor to check the request an this is it:
>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
>>        <soap:Body>
>>                <ns1:pago
>> xmlns:ns1="http://suramericana.contabilidad.test";>
>>                        <pago
>> xmlns:ns2="http://suramericana.contabilidad.test";
>>                              
>>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="pago">
>>                                <cajaResponsable>3</cajaResponsable>
>>                                <centroCosto>2492</centroCosto>
>>                                <cobrador>Juanda</cobrador>
>>                                <detalleAplicacionPagos>
>>                                        <codigoCliente>1</codigoCliente>
>>                                      
>>  <codigoCompania>epsSura</codigoCompania>
>>                                      
>>  <numeroDocumento>4747474</numeroDocumento>
>>                                      
>>  <numeroReciboCaja>2323</numeroReciboCaja>
>>                                </detalleAplicacionPagos>
>>                                <detalleConceptos>
>>                                        <compania>epsSura</compania>
>>                                        <cuenta>3232</cuenta>
>>                                        <division>///</division>
>>                                </detalleConceptos>
>>                                <detallePagos>
>>                                        <aprobacion>SI</aprobacion>
>>                                        <banco>Bancoco</banco>
>>                                        <codigoTarjeta>34</codigoTarjeta>
>>                                </detallePagos>
>>                                <idTransaccion>1</idTransaccion>
>>                                <sleep>10000</sleep>
>>                        </pago>
>>                </ns1:pago>
>>        </soap:Body>
>> </soap:Envelope>
>>
>>
>> the xsd for Pago goes like this:
>>
>> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>>        xmlns:bons1="http://suramericana.contabilidad.test";
>>        targetNamespace="http://suramericana.contabilidad.test";>
>>
>>        <xsd:include schemaLocation="DetalleAplicacionPago.xsd" />
>>        <xsd:include schemaLocation="DetalleConcepto.xsd" />
>>        <xsd:include schemaLocation="DetallePago.xsd" />
>>        <xsd:complexType name="Pago">
>>                <xsd:sequence>
>>                        <xsd:element minOccurs="0" name="control"
>>                                type="xsd:string">
>>
>> …………
>>
>>
>>
>>
>> I also try the eclipse web services test client and it works just fine,
>> this
>> is the request generated:
>>
>> <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:q0="http://suramericana.contabilidad.test";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>>  <soapenv:Body>
>>    <q0:pago>
>>      <pago>
>>        <control>13132</control>
>>        <secuencia>445</secuencia>
>>        <detallePagos>
>>          <control>78</control>
>>          <aprobacion>jkhkj</aprobacion>
>>        </detallePagos>
>>        <sleep>1000</sleep>
>>        <idTransaccion>47</idTransaccion>
>>      </pago>
>>    </q0:pago>
>>  </soapenv:Body>
>> </soapenv:Envelope>
>>
>>
>> I also try an Axys client and worked fine
>>
>> I got the same result using the DynamicClientFactory and the
>> JaxWsDynamicClientFactory
>>
>> I really appreciate if somebody can help me on this issue
>>
>> Thanks in advance
>> --
>> View this message in context:
>> http://www.nabble.com/CXF--client-fails-to-consume-a-WebSphere-Process-Server-service-tp25096399p25096399.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>>
> 
> 
http://www.nabble.com/file/p25119811/wsdl2.rar wsdl2.rar 
-- 
View this message in context: 
http://www.nabble.com/CXF--client-fails-to-consume-a-WebSphere-Process-Server-service-tp25096399p25119811.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to