Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 33786 invoked from network); 21 Oct 2009 11:38:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Oct 2009 11:38:38 -0000 Received: (qmail 50376 invoked by uid 500); 21 Oct 2009 11:38:38 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 50275 invoked by uid 500); 21 Oct 2009 11:38:37 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 50266 invoked by uid 99); 21 Oct 2009 11:38:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2009 11:38:37 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cchinu@gmail.com designates 209.85.216.203 as permitted sender) Received: from [209.85.216.203] (HELO mail-px0-f203.google.com) (209.85.216.203) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2009 11:38:35 +0000 Received: by pxi41 with SMTP id 41so7755853pxi.30 for ; Wed, 21 Oct 2009 04:38:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=aYynoznp7Rz5jtV2qCH1z3ojqW+o6CJk68pv9vFKOk4=; b=Bp12eceuNEs+T62RbXws2efBk1p7xc8xMvw7QmWmLIPDRxiC3ZjNPhkh7U+bT5Rfwz bWzfq+QR57xnkYvKlv46JEUMKtOMSRNal3MEP5+FcAPJ9eeOLN4UPLACSiDcH9elTp8G xPkI2yTbbF4ZiGgIl3RnG4w+PDm9GWPKFrwf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qGZCNP+DYHEkJtP8eFS4clmM6i9KDkQQDEqw/eYZOmWpmS5WUuxWKYmLChcaqs7YT9 kjbb6VhyezyrVhT5zFID9s8AvNMlNlIZiRVRH+slXiwDZ0r9zMkb8gkdGQF3r8d/khec 5jSsEF6De3WGvm5ruEsWJpuw4xA93buS5i7ak= MIME-Version: 1.0 Received: by 10.140.171.8 with SMTP id t8mr1662801rve.160.1256125094841; Wed, 21 Oct 2009 04:38:14 -0700 (PDT) In-Reply-To: <25987803.post@talk.nabble.com> References: <25987803.post@talk.nabble.com> Date: Wed, 21 Oct 2009 17:08:14 +0530 Message-ID: Subject: Re: Generating mutiple port names while generating WSDL using Axis2 Code generator eclipse plugin From: Chinmoy Chakraborty To: axis-dev@ws.apache.org Content-Type: multipart/alternative; boundary=000e0cd299e8124cf70476706a17 --000e0cd299e8124cf70476706a17 Content-Type: text/plain; charset=ISO-8859-1 Once I aksed this question and below is the answer I got from a developer: *Since Axis2 1.4 we have the concept of dispatching request to the endpoints not just to the service. The reason is that security scenarios could be configured on a endpoint level and hence we need to know the exact endpoint a request is headed to in order to apply the security scenario accordingly.* *This is the reason you see the unique addresses for each endpoint and it takes the form serviceName.endpointName.* In your case "http://localhost:8080/axis2/services/HelloWorld" should work. Chinmoy On Wed, Oct 21, 2009 at 1:05 PM, SivaKumarl wrote: > > Hi friends, > I am little bit cofusing the way WSDL is generating by Axis2 code > generator eclipse plugin, here it is generating three ports , kindly > explain > me why this is happening and how this port name will be use, please find > the > below sample xml code > > > xmlns:ns1="http://org.apache.axis2/xsd" > xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" > xmlns:xsd="http://test.ycs.com" xmlns:xs="http://www.w3.org/2001/XMLSchema > " > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" > targetNamespace="http://test.ycs.com"> > > elementFormDefault="qualified" targetNamespace="http://test.ycs.com"> > > > > type="xs:string"/> > > > > > > > nillable="true" type="xs:string"/> > > > > > > > > > > > > > > > wsaw:Action="urn:helloResponse"/> > > > type="xsd:HelloWorldPortType"> > style="document"/> > > > > > > > > > > > type="xsd:HelloWorldPortType"> > style="document"/> > > > > > > > > > > > type="xsd:HelloWorldPortType"> > > > > > > > > > > > > > binding="xsd:HelloWorldSoap11Binding"> > location="http://localhost:8080/axis2/services/HelloWorld"/> > > binding="xsd:HelloWorldSoap12Binding"> > location="http://localhost:8080/axis2/services/HelloWorld"/> > > binding="xsd:HelloWorldHttpBinding"> > location="http://localhost:8080/axis2/services/HelloWorld"/> > > > > > In above xml there are three portnames > HelloWorldHttpSoap11Endpoint,HelloWorldHttpSoap12Endpoint and > HelloWorldHttpEndpoint. > > Which port name will use by default. > > Thanks in Advance. > Siva > > -- > View this message in context: > http://www.nabble.com/Generating-mutiple-port-names-while-generating-WSDL-using-Axis2-Code-generator-eclipse-plugin-tp25987803p25987803.html > Sent from the Axis - Dev mailing list archive at Nabble.com. > > --000e0cd299e8124cf70476706a17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Once I aksed this question and below is the answer I got from a develo= per:
=A0
Since Axis2 1.4 we have the concept of dispatching request to the = endpoints not just to the service. The reason is that security scenarios co= uld be configured on a endpoint level and hence we need to know the exact e= ndpoint a request is headed to in order to apply the security scenario acco= rdingly.
This is the reason you see the unique addresses for each endpoint = and it takes the form serviceName.endpointName.
=A0
=A0
Chinmoy

On Wed, Oct 21, 2009 at 1:05 PM, SivaKumarl <sivakuma= rl@naradaproducts.com> wrote:

Hi friends,
=A0 =A0 =A0 = =A0 =A0I am little bit cofusing the way WSDL is generating by Axis2 codegenerator eclipse plugin, here it is generating three ports , kindly expla= in
me why this is happening and how this port name will be use, please find th= e
below sample xml code

<?xml version=3D"1.0" encodi= ng=3D"UTF-8"?>
<wsdl:definitions xmlns:wsdl=3D"http://schemas.x= mlsoap.org/wsdl/"
xmlns:ns1=3D"http://org.apache.axis2/xsd"
xmlns:wsaw=3D"http://www.w3.org= /2006/05/addressing/wsdl"
xmlns:http=3D"http://schemas.xmlsoap.org/wsdl/http/"
xmlns:xsd=3D= "http://test.ycs.co= m" xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
xmlns:mime=3D"http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap= =3D"http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12=3D"http://schemas.xmlsoap.org/wsdl/soap12/"
target= Namespace=3D"http:/= /test.ycs.com">
=A0 =A0<wsdl:types>
=A0 =A0 =A0 =A0<xs:schema attributeFormDefa= ult=3D"qualified"
elementFormDefault=3D"qualified" t= argetNamespace=3D"h= ttp://test.ycs.com">
=A0 =A0 =A0 =A0 =A0 =A0<xs:element name=3D"hello">
=A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0<xs:complexType>
=A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0<xs:sequence>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0<xs:element minOccurs=3D"0" name=3D"val&qu= ot; nillable=3D"true"
type=3D"xs:string"/>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0</xs:sequence>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</xs:complexTy= pe>
=A0 =A0 =A0 =A0 =A0 =A0</xs:element>
=A0 =A0 =A0 =A0 =A0= =A0<xs:element name=3D"helloResponse">
=A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0<xs:complexType>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<xs:sequence>
=A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<xs:element minOccurs=3D"0"= name=3D"return"
nillable=3D"true" type=3D"xs:s= tring"/>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</xs:sequence= >
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</xs:complexType>
=A0 =A0 =A0 =A0 = =A0 =A0</xs:element>
=A0 =A0 =A0 =A0</xs:schema>
=A0 =A0&= lt;/wsdl:types>
=A0 =A0<wsdl:message name=3D"helloRequest&quo= t;>
=A0 =A0 =A0 =A0<wsdl:part name=3D"parameters" elemen= t=3D"xsd:hello"/>
=A0 =A0</wsdl:message>
=A0 =A0<wsdl:message name=3D"helloR= esponse">
=A0 =A0 =A0 =A0<wsdl:part name=3D"parameters&q= uot; element=3D"xsd:helloResponse"/>
=A0 =A0</wsdl:messa= ge>
=A0 =A0<wsdl:portType name=3D"HelloWorldPortType">= ;
=A0 =A0 =A0 =A0<wsdl:operation name=3D"hello">
=A0 =A0 = =A0 =A0 =A0 =A0<wsdl:input message=3D"xsd:helloRequest" wsaw:A= ction=3D"urn:hello"/>
=A0 =A0 =A0 =A0 =A0 =A0<wsdl:outpu= t message=3D"xsd:helloResponse"
wsaw:Action=3D"urn:helloResponse"/>
=A0 =A0 =A0 =A0</wsd= l:operation>
=A0 =A0</wsdl:portType>
=A0 =A0<wsdl:binding= name=3D"HelloWorldSoap11Binding"
type=3D"xsd:HelloWorldP= ortType">
=A0 =A0 =A0 =A0<soap:binding transport=3D"http://schemas.xmlsoap.org/soap/h= ttp"
style=3D"document"/>
=A0 =A0 =A0 =A0<ws= dl:operation name=3D"hello">
=A0 =A0 =A0 =A0 =A0 =A0<soap:operation soapAction=3D"urn:hello"= ; style=3D"document"/>
=A0 =A0 =A0 =A0 =A0 =A0<wsdl:inpu= t>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<soap:body use=3D"literal&q= uot;/>
=A0 =A0 =A0 =A0 =A0 =A0</wsdl:input>
=A0 =A0 =A0 =A0 =A0 =A0<wsdl:output>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0<soap:body use=3D"literal"/>
=A0 =A0 =A0 =A0 =A0 =A0&= lt;/wsdl:output>
=A0 =A0 =A0 =A0</wsdl:operation>
=A0 =A0<= ;/wsdl:binding>
=A0 =A0<wsdl:binding name=3D"HelloWorldSoap12= Binding"
type=3D"xsd:HelloWorldPortType">
=A0 =A0 =A0 =A0<soap12:= binding transport=3D"http://schemas.xmlsoap.org/soap/http"
style= =3D"document"/>
=A0 =A0 =A0 =A0<wsdl:operation name=3D"hello">
=A0 =A0 = =A0 =A0 =A0 =A0<soap12:operation soapAction=3D"urn:hello" styl= e=3D"document"/>
=A0 =A0 =A0 =A0 =A0 =A0<wsdl:input><= br>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<soap12:body use=3D"literal"= />
=A0 =A0 =A0 =A0 =A0 =A0</wsdl:input>
=A0 =A0 =A0 =A0 =A0 =A0<ws= dl:output>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<soap12:body use=3D"= ;literal"/>
=A0 =A0 =A0 =A0 =A0 =A0</wsdl:output>
=A0 = =A0 =A0 =A0</wsdl:operation>
=A0 =A0</wsdl:binding>
=A0 =A0<wsdl:binding name=3D"HelloWorldHttpBinding"
type=3D= "xsd:HelloWorldPortType">
=A0 =A0 =A0 =A0<http:binding v= erb=3D"POST"/>
=A0 =A0 =A0 =A0<wsdl:operation name=3D&qu= ot;hello">
=A0 =A0 =A0 =A0 =A0 =A0<http:operation location=3D= "HelloWorld/hello"/>
=A0 =A0 =A0 =A0 =A0 =A0<wsdl:input>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0<mime:content type=3D"text/xml" part=3D"hello"/&g= t;
=A0 =A0 =A0 =A0 =A0 =A0</wsdl:input>
=A0 =A0 =A0 =A0 =A0 =A0= <wsdl:output>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<mime:content type= =3D"text/xml" part=3D"hello"/>
=A0 =A0 =A0 =A0 =A0 =A0</wsdl:output>
=A0 =A0 =A0 =A0</wsdl:ope= ration>
=A0 =A0</wsdl:binding>
=A0 =A0<wsdl:service name= =3D"HelloWorld">
=A0 =A0 =A0 =A0<wsdl:port name=3D"= HelloWorldHttpSoap11Endpoint"
binding=3D"xsd:HelloWorldSoap11Binding">
=A0 =A0 =A0 =A0 = =A0 =A0<soap:address
location=3D"http://localhost:8080/axis2/= services/HelloWorld"/>
=A0 =A0 =A0 =A0</wsdl:port>
=A0 =A0 =A0 =A0<wsdl:port name=3D&q= uot;HelloWorldHttpSoap12Endpoint"
binding=3D"xsd:HelloWorldSoa= p12Binding">
=A0 =A0 =A0 =A0 =A0 =A0<soap12:address
locati= on=3D"http://localhost:8080/axis2/services/HelloWorld"/>= ;
=A0 =A0 =A0 =A0</wsdl:port>
=A0 =A0 =A0 =A0<wsdl:port name=3D&q= uot;HelloWorldHttpEndpoint"
binding=3D"xsd:HelloWorldHttpBindi= ng">
=A0 =A0 =A0 =A0 =A0 =A0<http:address
location=3D"= ;http://localhost:8080/axis2/services/HelloWorld"/>
=A0 =A0 =A0 =A0</wsdl:port>
=A0 =A0</wsdl:service>
</w= sdl:definitions>

=A0In above xml there are three portnames
Hel= loWorldHttpSoap11Endpoint,HelloWorldHttpSoap12Endpoint and
HelloWorldHtt= pEndpoint.

=A0Which port name will use by default.

Thanks in Advance.
Si= va

--
View this message in context: http://www.nabble.com/Generating-mutiple-port-names-while-g= enerating-WSDL-using-Axis2-Code-generator-eclipse-plugin-tp25987803p2598780= 3.html
Sent from the Axis - Dev mailing list archive at Nabble.com.

=

--000e0cd299e8124cf70476706a17--