'[axis1 servers vs axis2 client] no such operation exception received until WSDL is seen'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-user
Subject:    [axis1 servers vs axis2 client] no such operation exception received until WSDL is seen
From:       JOSE L MARTINEZ-AVIAL <jlmagc () gmail ! com>
Date:       2012-05-09 3:16:40
Message-ID: CAHB4ARtt_cERhiNOmEAM1aK=ek4dkqPj005WTAd68FmXC35mwQ () mail ! gmail ! com
[Download RAW message or body]

Hello all,
  We want to generate an Axis2 client (1.6.1) client for an old Axis1
service. The service is a plain POJO, and the server-config.wsdd is as
follows:

    <service name="ValuationsXMLGenerator" provider="java:RPC"
style="document" use="literal">
        <parameter name="wsdlTargetNamespace" value="urn:xml.generator.ws"/>
        <parameter name="schemaUnqualified" value="urn:xml.generator.ws"/>

        <parameter name="className"
value="com.bpi.stmts.generacion.WSGenerator"/>
        <parameter name="extraClasses"
value="com.bpi.stmts.generacion.vo.XMLRequestBase"/>
        <parameter name="allowedMethods" value="generateCurrentXML"/>


        <operation name="generateCurrentXML" qname="generateCurrentXML"
returnQName="CurrentXMLResponse" returnType="rtns:XMLResponse"
xmlns:rtns="urn:xml.generator.ws" soapAction="generateCurrentXML">
            <parameter qname="CurrentXMLRequest" xmlns:pns="urn:
xml.generator.ws" type="tns:CurrentXMLRequest" xmlns:tns="urn:
xml.generator.ws"/>
        </operation>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:XMLRequestBase"
        type="java:com.bpi.stmts.generacion.vo.XMLRequestBase"/>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:XMLResponse"
        type="java:com.bpi.stmts.generacion.vo.XMLResponse"/>

        <beanMapping xmlns:ns="urn:xml.generator.ws"
            qname="ns:CurrentXMLRequest"
        type="java:com.bpi.stmts.generacion.vo.CurrentXMLRequest"/>

    </service>

The Axis2 client is created using the WSDL generated by Axis1 online. The
issue we have found is that when the server is restarted, the service
answers to any request to execute the method generateCurrentXML with a No
Such Operation exception, as follows:

<soapenv:Fault>
<faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Client</faultcode>
<faultstring>No such operation 'CurrentXMLRequest'</faultstring>
<detail>
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/
">myserver</ns2:hostname>
</detail>
</soapenv:Fault>

This happens until someone queries the URL
http://myserver/myapp/services/ValuationsXMLGenerator?wsdl. Then all the
request go through, and they are answered correctly. Has anyone see this
behavior before? if so, is there any way to fix it?

thanks

[Attachment #3 (text/html)]

Hello all,<br>  We want to generate an Axis2 client (1.6.1) client for an old Axis1 \
service. The service is a plain POJO, and the server-config.wsdd is as \
follows:<br><br>    &lt;service name=&quot;ValuationsXMLGenerator&quot; \
provider=&quot;java:RPC&quot; style=&quot;document&quot; \
use=&quot;literal&quot;&gt;<br>  &lt;parameter name=&quot;wsdlTargetNamespace&quot; \
value=&quot;urn:<a href="http://xml.generator.ws">xml.generator.ws</a>&quot;/&gt;<br> \
&lt;parameter name=&quot;schemaUnqualified&quot; value=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot;/&gt;<br> <br>        \
&lt;parameter name=&quot;className&quot; \
value=&quot;com.bpi.stmts.generacion.WSGenerator&quot;/&gt;<br>        &lt;parameter \
name=&quot;extraClasses&quot; \
value=&quot;com.bpi.stmts.generacion.vo.XMLRequestBase&quot;/&gt;<br>  &lt;parameter \
name=&quot;allowedMethods&quot; value=&quot;generateCurrentXML&quot;/&gt;<br><br><br> \
&lt;operation name=&quot;generateCurrentXML&quot; \
qname=&quot;generateCurrentXML&quot; returnQName=&quot;CurrentXMLResponse&quot; \
returnType=&quot;rtns:XMLResponse&quot; xmlns:rtns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot; \
soapAction=&quot;generateCurrentXML&quot;&gt;<br>  &lt;parameter \
qname=&quot;CurrentXMLRequest&quot; xmlns:pns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot; \
type=&quot;tns:CurrentXMLRequest&quot; xmlns:tns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot;/&gt;<br>  \
&lt;/operation&gt;<br><br>        &lt;beanMapping xmlns:ns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot;<br>            \
qname=&quot;ns:XMLRequestBase&quot;<br>        \
type=&quot;java:com.bpi.stmts.generacion.vo.XMLRequestBase&quot;/&gt;<br> <br>        \
&lt;beanMapping xmlns:ns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot;<br>            \
qname=&quot;ns:XMLResponse&quot;<br>        \
type=&quot;java:com.bpi.stmts.generacion.vo.XMLResponse&quot;/&gt;<br> <br>        \
&lt;beanMapping xmlns:ns=&quot;urn:<a \
href="http://xml.generator.ws">xml.generator.ws</a>&quot;<br>            \
qname=&quot;ns:CurrentXMLRequest&quot;<br>        \
type=&quot;java:com.bpi.stmts.generacion.vo.CurrentXMLRequest&quot;/&gt;<br> <br>    \
&lt;/service&gt;<br><br>The Axis2 client is created using the WSDL generated by Axis1 \
online. The issue we have found is that when the server is restarted, the service \
answers to any request to execute the method generateCurrentXML with a No Such \
Operation exception, as follows:<br> <br>&lt;soapenv:Fault&gt;<br>&lt;faultcode \
xmlns:ns1=&quot;<a href="http://xml.apache.org/axis/">http://xml.apache.org/axis/</a>&quot;&gt;ns1:Client&lt;/faultcode&gt;<br>&lt;faultstring&gt;No \
such operation &#39;CurrentXMLRequest&#39;&lt;/faultstring&gt;<br> \
&lt;detail&gt;<br>&lt;ns2:hostname xmlns:ns2=&quot;<a \
href="http://xml.apache.org/axis/">http://xml.apache.org/axis/</a>&quot;&gt;myserver&lt;/ns2:hostname&gt;<br>&lt;/detail&gt;<br>&lt;/soapenv:Fault&gt;<br><br>This \
happens until someone queries the URL <a \
href="http://myserver/myapp/services/ValuationsXMLGenerator?wsdl">http://myserver/myapp/services/ValuationsXMLGenerator?wsdl</a>. \
Then all the request go through, and they are answered correctly. Has anyone see this \
behavior before? if so, is there any way to fix it?<br> <br>thanks<br>



[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic