You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Roland Sperl <Ro...@METAFINANZ.DE> on 2008/02/22 11:45:58 UTC
AW: Problems with SOAP-Request - threading problem?
Hi Guillaume,
I've debugged my Problem deep into the section where the JSR181 uses the xfire-classes to map the delivered parameters into the operation signature of my service. I can see that the 3 parameters are delivered correctly to the Jsr181ExchangeProcessor but only 2 parameters (1st, 3rd) arrives in the org.codehaus.xfire.service.binding.ServiceInvocationHandler and that causes the exception. The confusing part is that from to time during debugging I can see the 3 right paramaters in the ServiceInvocationHandler and everything is o.k. - but this behaviour doesn't occur in a deterministic way. I didn't find the code section where the missing parameter disappears.
Could it be an threading problem?
Regards
Roland
-----Ursprüngliche Nachricht-----
Von: Roland Sperl [mailto:Roland.Sperl@METAFINANZ.DE]
Gesendet: Freitag, 22. Februar 2008 09:27
An: users@servicemix.apache.org
Betreff: AW: Problems with SOAP-Request
Hi,
style="document" ends in:
STATUS: 500
<?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Server</faultcode><faultstring>Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
at [row,col {unknown-source}]: [12,7]</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
at [row,col {unknown-source}]: [12,7]
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.transport.DefaultEndpoint.onReceive
typeMapping="default" ends in my old problem:
STATUS: 400
<?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>Not enough message parts were received for the operation.</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Not enough message parts were received for the operation.
at org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHolders(ServiceInvocationHandler.java:240)
Thx in advance
Roland
-----Ursprüngliche Nachricht-----
Von: Guillaume Nodet [mailto:gnodet@gmail.com]
Gesendet: Donnerstag, 21. Februar 2008 17:50
An: users@servicemix.apache.org
Betreff: Re: Problems with SOAP-Request
Did you configure the endpoint to use doc/lit:
<jsr181:endpoint style="document" ...>
maybe you can try setting the typeMapping="aegis" ?
On Thu, Feb 21, 2008 at 4:37 PM, Roland Sperl
<Ro...@metafinanz.de> wrote:
> Hi Guillaume,
>
> thx for your quick answer.
>
> Here is the wsdl, the format ist xsd:string which should be correct.
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo">
> - <wsdl:types>
> - <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> - <xsd:element name="transform">
> - <xsd:complexType>
> - <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string" />
> <xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="xsd:string" />
> <xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true" type="xsd:string" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> - <xsd:element name="transformResponse">
> - <xsd:complexType>
> - <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="xsd:string" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> </wsdl:types>
> - <wsdl:message name="transformRequest">
> <wsdl:part element="tns:transform" name="parameters" />
> </wsdl:message>
> - <wsdl:message name="transformResponse">
> <wsdl:part element="tns:transformResponse" name="parameters" />
> </wsdl:message>
> - <wsdl:portType name="transformEnginePortType">
> - <wsdl:operation name="transform">
> <wsdl:input message="tns:transformRequest" name="transformRequest" />
> <wsdl:output message="tns:transformResponse" name="transformResponse" />
> </wsdl:operation>
> </wsdl:portType>
> - <wsdl:binding name="httpConsumerBinding" type="tns:transformEnginePortType">
> <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
> - <wsdl:operation name="transform">
> <wsdlsoap:operation soapAction="" />
> - <wsdl:input name="transformRequest">
> <wsdlsoap:body use="literal" />
> </wsdl:input>
> - <wsdl:output name="transformResponse">
> <wsdlsoap:body use="literal" />
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
> - <wsdl:service name="httpConsumer">
> - <wsdl:port binding="tns:httpConsumerBinding" name="httpConsumer">
> <wsdlsoap:address location="http://localhost:8081/services/XSLTEngine/" />
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
> -----Ursprüngliche Nachricht-----
> Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> Gesendet: Donnerstag, 21. Februar 2008 16:31
> An: users@servicemix.apache.org
> Betreff: Re: Problems with SOAP-Request
>
>
>
> Can you check against the WSDL for the jsr181 endpoint ?
> You should be able to access it from jconsole by looking at the http endpoint
> in your browser. It should defines the format of the expected data.
>
> On Thu, Feb 21, 2008 at 4:27 PM, Roland Sperl
> <Ro...@metafinanz.de> wrote:
> > Hi All!
> >
> > I deployed a simple Pojo into the JSR181 with the following Interface:
> >
> > public String transform(String fromAccountId, String toAccount, String
> > amount);
> >
> > I have build a html-client which calls the Pojo with the following
> > SOAP-Call:
> >
> > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:n1="java:de.metafinanz.sca.BankTransaction"
> >
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >
> > xmlns:transactionRequest="http://www.metafinanz.org/transform/"
> > xsi:type="n1:TransactionRequest">
> >
> > <env:Body>
> > <transactionRequest:transform>
> > <in0>1</in0>
> > <in1>2</in1>
> > <in2>100</in2>
> > </transactionRequest:transform>
> > </env:Body>
> >
> > </env:Envelope>
> >
> > I thought that the values in the parameters would be automatically set
> > into my pojo parameters, but I get the exception:
> >
> > org.codehaus.xfire.fault.XFireFault: Not enough message parts were
> > received for the operation.
> > at org.codehaus.xfire.service.binding.ServiceInvocationHandler
> > ...
> >
> > If I put 5 parameters between the <transactionRequest:transform> tag the
> > values are passed to my pojo. But in an confusing way, the 1st, 3rd and
> > 5th value are passed to my pojo.
> >
> > Can anyone help me?
> >
> > Thanks in advance
> > Roland
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
AW: Problems with SOAP-Request - threading problem?
Posted by Roland Sperl <Ro...@METAFINANZ.DE>.
In the meanwhile I focused the problem to the STAXUtil-Class which is accessed via static method calls.
I have another question about the xbean configuration of cxf-se because the defined servicename and endpointname is not recognized:
<beans xmlns:cxfse="http://servicemix.apache.org/cxfse/1.0"
xmlns:test="http://de.metafinanz.sca.java.pojo.transform/jsrpojo">
<cxfse:endpoint service="test:transformEngine"
endpoint="transformEngine">
<cxfse:pojo>
<bean class="de.metafinanz.sca.java.pojo.transform.XSLTEngineImpl">
</bean>
</cxfse:pojo>
</cxfse:endpoint>
</beans>
Is there something wrong with this definition?
Thx in advance
Roland
-----Ursprüngliche Nachricht-----
Von: Guillaume Nodet [mailto:gnodet@gmail.com]
Gesendet: Freitag, 22. Februar 2008 13:00
An: users@servicemix.apache.org
Betreff: Re: Problems with SOAP-Request - threading problem?
I'm not aware of anything like that and I've never seen any threading
problem in jsr181 (that does not mean there are no problems at all of
course).
Maybe you should try with cxf-se instead, because xfire is not
developed anymore.
On Fri, Feb 22, 2008 at 11:45 AM, Roland Sperl
<Ro...@metafinanz.de> wrote:
> Hi Guillaume,
>
> I've debugged my Problem deep into the section where the JSR181 uses the xfire-classes to map the delivered parameters into the operation signature of my service. I can see that the 3 parameters are delivered correctly to the Jsr181ExchangeProcessor but only 2 parameters (1st, 3rd) arrives in the org.codehaus.xfire.service.binding.ServiceInvocationHandler and that causes the exception. The confusing part is that from to time during debugging I can see the 3 right paramaters in the ServiceInvocationHandler and everything is o.k. - but this behaviour doesn't occur in a deterministic way. I didn't find the code section where the missing parameter disappears.
>
> Could it be an threading problem?
>
> Regards
> Roland
>
> -----Ursprüngliche Nachricht-----
> Von: Roland Sperl [mailto:Roland.Sperl@METAFINANZ.DE]
> Gesendet: Freitag, 22. Februar 2008 09:27
> An: users@servicemix.apache.org
> Betreff: AW: Problems with SOAP-Request
>
> Hi,
>
> style="document" ends in:
>
> STATUS: 500
> <?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Server</faultcode><faultstring>Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
> at [row,col {unknown-source}]: [12,7]</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
> at [row,col {unknown-source}]: [12,7]
> at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
> at org.codehaus.xfire.transport.DefaultEndpoint.onReceive
>
>
> typeMapping="default" ends in my old problem:
>
> STATUS: 400
> <?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>Not enough message parts were received for the operation.</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Not enough message parts were received for the operation.
> at org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHolders(ServiceInvocationHandler.java:240)
>
> Thx in advance
>
> Roland
>
> -----Ursprüngliche Nachricht-----
> Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> Gesendet: Donnerstag, 21. Februar 2008 17:50
> An: users@servicemix.apache.org
> Betreff: Re: Problems with SOAP-Request
>
> Did you configure the endpoint to use doc/lit:
>
> <jsr181:endpoint style="document" ...>
>
> maybe you can try setting the typeMapping="aegis" ?
>
> On Thu, Feb 21, 2008 at 4:37 PM, Roland Sperl
> <Ro...@metafinanz.de> wrote:
> > Hi Guillaume,
> >
> > thx for your quick answer.
> >
> > Here is the wsdl, the format ist xsd:string which should be correct.
> >
> > <?xml version="1.0" encoding="UTF-8" ?>
> > - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo">
> > - <wsdl:types>
> > - <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > - <xsd:element name="transform">
> > - <xsd:complexType>
> > - <xsd:sequence>
> > <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string" />
> > <xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="xsd:string" />
> > <xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > - <xsd:element name="transformResponse">
> > - <xsd:complexType>
> > - <xsd:sequence>
> > <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </wsdl:types>
> > - <wsdl:message name="transformRequest">
> > <wsdl:part element="tns:transform" name="parameters" />
> > </wsdl:message>
> > - <wsdl:message name="transformResponse">
> > <wsdl:part element="tns:transformResponse" name="parameters" />
> > </wsdl:message>
> > - <wsdl:portType name="transformEnginePortType">
> > - <wsdl:operation name="transform">
> > <wsdl:input message="tns:transformRequest" name="transformRequest" />
> > <wsdl:output message="tns:transformResponse" name="transformResponse" />
> > </wsdl:operation>
> > </wsdl:portType>
> > - <wsdl:binding name="httpConsumerBinding" type="tns:transformEnginePortType">
> > <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
> > - <wsdl:operation name="transform">
> > <wsdlsoap:operation soapAction="" />
> > - <wsdl:input name="transformRequest">
> > <wsdlsoap:body use="literal" />
> > </wsdl:input>
> > - <wsdl:output name="transformResponse">
> > <wsdlsoap:body use="literal" />
> > </wsdl:output>
> > </wsdl:operation>
> > </wsdl:binding>
> > - <wsdl:service name="httpConsumer">
> > - <wsdl:port binding="tns:httpConsumerBinding" name="httpConsumer">
> > <wsdlsoap:address location="http://localhost:8081/services/XSLTEngine/" />
> > </wsdl:port>
> > </wsdl:service>
> > </wsdl:definitions>
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> > Gesendet: Donnerstag, 21. Februar 2008 16:31
> > An: users@servicemix.apache.org
> > Betreff: Re: Problems with SOAP-Request
> >
> >
> >
> > Can you check against the WSDL for the jsr181 endpoint ?
> > You should be able to access it from jconsole by looking at the http endpoint
> > in your browser. It should defines the format of the expected data.
> >
> > On Thu, Feb 21, 2008 at 4:27 PM, Roland Sperl
> > <Ro...@metafinanz.de> wrote:
> > > Hi All!
> > >
> > > I deployed a simple Pojo into the JSR181 with the following Interface:
> > >
> > > public String transform(String fromAccountId, String toAccount, String
> > > amount);
> > >
> > > I have build a html-client which calls the Pojo with the following
> > > SOAP-Call:
> > >
> > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > > xmlns:n1="java:de.metafinanz.sca.BankTransaction"
> > >
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > >
> > > xmlns:transactionRequest="http://www.metafinanz.org/transform/"
> > > xsi:type="n1:TransactionRequest">
> > >
> > > <env:Body>
> > > <transactionRequest:transform>
> > > <in0>1</in0>
> > > <in1>2</in1>
> > > <in2>100</in2>
> > > </transactionRequest:transform>
> > > </env:Body>
> > >
> > > </env:Envelope>
> > >
> > > I thought that the values in the parameters would be automatically set
> > > into my pojo parameters, but I get the exception:
> > >
> > > org.codehaus.xfire.fault.XFireFault: Not enough message parts were
> > > received for the operation.
> > > at org.codehaus.xfire.service.binding.ServiceInvocationHandler
> > > ...
> > >
> > > If I put 5 parameters between the <transactionRequest:transform> tag the
> > > values are passed to my pojo. But in an confusing way, the 1st, 3rd and
> > > 5th value are passed to my pojo.
> > >
> > > Can anyone help me?
> > >
> > > Thanks in advance
> > > Roland
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Problems with SOAP-Request - threading problem?
Posted by Guillaume Nodet <gn...@gmail.com>.
I'm not aware of anything like that and I've never seen any threading
problem in jsr181 (that does not mean there are no problems at all of
course).
Maybe you should try with cxf-se instead, because xfire is not
developed anymore.
On Fri, Feb 22, 2008 at 11:45 AM, Roland Sperl
<Ro...@metafinanz.de> wrote:
> Hi Guillaume,
>
> I've debugged my Problem deep into the section where the JSR181 uses the xfire-classes to map the delivered parameters into the operation signature of my service. I can see that the 3 parameters are delivered correctly to the Jsr181ExchangeProcessor but only 2 parameters (1st, 3rd) arrives in the org.codehaus.xfire.service.binding.ServiceInvocationHandler and that causes the exception. The confusing part is that from to time during debugging I can see the 3 right paramaters in the ServiceInvocationHandler and everything is o.k. - but this behaviour doesn't occur in a deterministic way. I didn't find the code section where the missing parameter disappears.
>
> Could it be an threading problem?
>
> Regards
> Roland
>
> -----Ursprüngliche Nachricht-----
> Von: Roland Sperl [mailto:Roland.Sperl@METAFINANZ.DE]
> Gesendet: Freitag, 22. Februar 2008 09:27
> An: users@servicemix.apache.org
> Betreff: AW: Problems with SOAP-Request
>
> Hi,
>
> style="document" ends in:
>
> STATUS: 500
> <?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Server</faultcode><faultstring>Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
> at [row,col {unknown-source}]: [12,7]</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Could not read XML stream.. Nested exception is com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
> at [row,col {unknown-source}]: [12,7]
> at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
> at org.codehaus.xfire.transport.DefaultEndpoint.onReceive
>
>
> typeMapping="default" ends in my old problem:
>
> STATUS: 400
> <?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>Not enough message parts were received for the operation.</faultstring><detail><stack>org.codehaus.xfire.fault.XFireFault: Not enough message parts were received for the operation.
> at org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHolders(ServiceInvocationHandler.java:240)
>
> Thx in advance
>
> Roland
>
> -----Ursprüngliche Nachricht-----
> Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> Gesendet: Donnerstag, 21. Februar 2008 17:50
> An: users@servicemix.apache.org
> Betreff: Re: Problems with SOAP-Request
>
> Did you configure the endpoint to use doc/lit:
>
> <jsr181:endpoint style="document" ...>
>
> maybe you can try setting the typeMapping="aegis" ?
>
> On Thu, Feb 21, 2008 at 4:37 PM, Roland Sperl
> <Ro...@metafinanz.de> wrote:
> > Hi Guillaume,
> >
> > thx for your quick answer.
> >
> > Here is the wsdl, the format ist xsd:string which should be correct.
> >
> > <?xml version="1.0" encoding="UTF-8" ?>
> > - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo">
> > - <wsdl:types>
> > - <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://de.metafinanz.sca.java.pojo.transform/jsrpojo" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > - <xsd:element name="transform">
> > - <xsd:complexType>
> > - <xsd:sequence>
> > <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string" />
> > <xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="xsd:string" />
> > <xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > - <xsd:element name="transformResponse">
> > - <xsd:complexType>
> > - <xsd:sequence>
> > <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </wsdl:types>
> > - <wsdl:message name="transformRequest">
> > <wsdl:part element="tns:transform" name="parameters" />
> > </wsdl:message>
> > - <wsdl:message name="transformResponse">
> > <wsdl:part element="tns:transformResponse" name="parameters" />
> > </wsdl:message>
> > - <wsdl:portType name="transformEnginePortType">
> > - <wsdl:operation name="transform">
> > <wsdl:input message="tns:transformRequest" name="transformRequest" />
> > <wsdl:output message="tns:transformResponse" name="transformResponse" />
> > </wsdl:operation>
> > </wsdl:portType>
> > - <wsdl:binding name="httpConsumerBinding" type="tns:transformEnginePortType">
> > <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
> > - <wsdl:operation name="transform">
> > <wsdlsoap:operation soapAction="" />
> > - <wsdl:input name="transformRequest">
> > <wsdlsoap:body use="literal" />
> > </wsdl:input>
> > - <wsdl:output name="transformResponse">
> > <wsdlsoap:body use="literal" />
> > </wsdl:output>
> > </wsdl:operation>
> > </wsdl:binding>
> > - <wsdl:service name="httpConsumer">
> > - <wsdl:port binding="tns:httpConsumerBinding" name="httpConsumer">
> > <wsdlsoap:address location="http://localhost:8081/services/XSLTEngine/" />
> > </wsdl:port>
> > </wsdl:service>
> > </wsdl:definitions>
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> > Gesendet: Donnerstag, 21. Februar 2008 16:31
> > An: users@servicemix.apache.org
> > Betreff: Re: Problems with SOAP-Request
> >
> >
> >
> > Can you check against the WSDL for the jsr181 endpoint ?
> > You should be able to access it from jconsole by looking at the http endpoint
> > in your browser. It should defines the format of the expected data.
> >
> > On Thu, Feb 21, 2008 at 4:27 PM, Roland Sperl
> > <Ro...@metafinanz.de> wrote:
> > > Hi All!
> > >
> > > I deployed a simple Pojo into the JSR181 with the following Interface:
> > >
> > > public String transform(String fromAccountId, String toAccount, String
> > > amount);
> > >
> > > I have build a html-client which calls the Pojo with the following
> > > SOAP-Call:
> > >
> > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> > > xmlns:n1="java:de.metafinanz.sca.BankTransaction"
> > >
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > >
> > > xmlns:transactionRequest="http://www.metafinanz.org/transform/"
> > > xsi:type="n1:TransactionRequest">
> > >
> > > <env:Body>
> > > <transactionRequest:transform>
> > > <in0>1</in0>
> > > <in1>2</in1>
> > > <in2>100</in2>
> > > </transactionRequest:transform>
> > > </env:Body>
> > >
> > > </env:Envelope>
> > >
> > > I thought that the values in the parameters would be automatically set
> > > into my pojo parameters, but I get the exception:
> > >
> > > org.codehaus.xfire.fault.XFireFault: Not enough message parts were
> > > received for the operation.
> > > at org.codehaus.xfire.service.binding.ServiceInvocationHandler
> > > ...
> > >
> > > If I put 5 parameters between the <transactionRequest:transform> tag the
> > > values are passed to my pojo. But in an confusing way, the 1st, 3rd and
> > > 5th value are passed to my pojo.
> > >
> > > Can anyone help me?
> > >
> > > Thanks in advance
> > > Roland
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/