You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Daniel Woo <da...@gmail.com> on 2008/03/20 07:31:44 UTC

axis 1.3 generated WSDL with three ports/bindings?

Hi,

I am a green babie with SOAP, my problem is that when I deploy a POJO
service class axis automatically generates a WSDL, but the generated WSDL
contains three bindings, eg

<wsdl:service name="ProblemService">
    <wsdl:port name="ProblemServiceHttpSoap11Endpoint"
binding="ns:ProblemServiceHttpSoap11Binding">
        <soap:address location="
http://16.158.65.18:80/axis2/services/ProblemService"/>
    </wsdl:port>
    <wsdl:port name="ProblemServiceHttpSoap12Endpoint"
binding="ns:ProblemServiceHttpSoap12Binding">
        <soap12:address location="
http://16.158.65.18:80/axis2/services/ProblemService"/>
    </wsdl:port>
    <wsdl:port name="ProblemServiceHttpEndpoint"
binding="ns:ProblemServiceHttpBinding">
        <http:address location="
http://16.158.65.18:80/axis2/services/ProblemService"/>
    </wsdl:port>
</wsdl:service>

Then my question is that why three ports/bindings we need? I can't see any
difference between the three bindings. When a SOAP request is incoming,
which port/binding will be used?

-- 
Thanks & Regards,
Daniel

Re: axis 1.3 generated WSDL with three ports/bindings?

Posted by Daniel Woo <da...@gmail.com>.
Hi Nadir,

Really thanks.

On Thu, Mar 20, 2008 at 10:11 PM, Nadir Amra <am...@us.ibm.com> wrote:

> Daniel,
>
> One for SOAP 1.1, one for SOAP 1.2, and one for REST-like Web services.
> You can suppress 1.2 and REST like SOAP bindings by turning a flag on or
> off in Axis2.xml,  as follows:
>
> - <!--
>  Following parameter will completely disable REST handling in Axis2
>  -->
>  <parameter name="disableREST" locked="true">true</parameter>
> - <!--
>  Following parameter will suppress generation of SOAP 1.2 bindings in
> auto-generated WSDL files
>  -->
>  <parameter name="disableSOAP12" locked="true">true</parameter>
>
>
>
> Nadir Amra
>
>
> "Daniel Woo" <da...@gmail.com> wrote on 03/20/2008 01:31:44 AM:
>
> > Hi,
> >
> > I am a green babie with SOAP, my problem is that when I deploy a
> > POJO service class axis automatically generates a WSDL, but the
> > generated WSDL contains three bindings, eg
> >
> > <wsdl:service name="ProblemService">
> >     <wsdl:port name="ProblemServiceHttpSoap11Endpoint" binding="ns:
> > ProblemServiceHttpSoap11Binding">
> >         <soap:address location="http://16.158.65.18:
> > 80/axis2/services/ProblemService"/>
> >     </wsdl:port>
> >     <wsdl:port name="ProblemServiceHttpSoap12Endpoint" binding="ns:
> > ProblemServiceHttpSoap12Binding">
> >         <soap12:address location="http://16.158.65.18:
> > 80/axis2/services/ProblemService"/>
> >     </wsdl:port>
> >     <wsdl:port name="ProblemServiceHttpEndpoint" binding="ns:
> > ProblemServiceHttpBinding">
> >         <http:address location="http://16.158.65.18:
> > 80/axis2/services/ProblemService"/>
> >     </wsdl:port>
> > </wsdl:service>
> >
> > Then my question is that why three ports/bindings we need? I can't
> > see any difference between the three bindings. When a SOAP request
> > is incoming, which port/binding will be used?
> >
> > --
> > Thanks & Regards,
> > Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Thanks & Regards,
Daniel

Re: axis 1.3 generated WSDL with three ports/bindings?

Posted by Nadir Amra <am...@us.ibm.com>.
Daniel,

One for SOAP 1.1, one for SOAP 1.2, and one for REST-like Web services. 
You can suppress 1.2 and REST like SOAP bindings by turning a flag on or 
off in Axis2.xml,  as follows:

- <!-- 
 Following parameter will completely disable REST handling in Axis2
  --> 
  <parameter name="disableREST" locked="true">true</parameter> 
- <!-- 
 Following parameter will suppress generation of SOAP 1.2 bindings in 
auto-generated WSDL files 
  --> 
  <parameter name="disableSOAP12" locked="true">true</parameter> 



Nadir Amra


"Daniel Woo" <da...@gmail.com> wrote on 03/20/2008 01:31:44 AM:

> Hi,
> 
> I am a green babie with SOAP, my problem is that when I deploy a 
> POJO service class axis automatically generates a WSDL, but the 
> generated WSDL contains three bindings, eg
> 
> <wsdl:service name="ProblemService">
>     <wsdl:port name="ProblemServiceHttpSoap11Endpoint" binding="ns:
> ProblemServiceHttpSoap11Binding">
>         <soap:address location="http://16.158.65.18:
> 80/axis2/services/ProblemService"/>
>     </wsdl:port>
>     <wsdl:port name="ProblemServiceHttpSoap12Endpoint" binding="ns:
> ProblemServiceHttpSoap12Binding">
>         <soap12:address location="http://16.158.65.18:
> 80/axis2/services/ProblemService"/>
>     </wsdl:port>
>     <wsdl:port name="ProblemServiceHttpEndpoint" binding="ns:
> ProblemServiceHttpBinding">
>         <http:address location="http://16.158.65.18:
> 80/axis2/services/ProblemService"/>
>     </wsdl:port>
> </wsdl:service>
> 
> Then my question is that why three ports/bindings we need? I can't 
> see any difference between the three bindings. When a SOAP request 
> is incoming, which port/binding will be used?
> 
> -- 
> Thanks & Regards,
> Daniel 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org