Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Subject: [Axis2] Providing custom WSDL
To: axis-user@ws.apache.org
Message-ID: 
 <OFF41B1602.8DFCBF45-ON8525716C.0057F380-8525716C.00597275@mro.com>
From: Junaid.Bhatra@mro.com
Date: Fri, 12 May 2006 12:17:01 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Hi all,

I'm deploying my Web Service using the RawXMLINOutMessageReceiver and
providing my own WSDL in the META-INF folder. However the WSDL that is
returned from the ?wsdl URL is different than the original one,
specifically the <wsdl:binding> and <wsdl:service> portions are changed.
What is the rationale behind this? I can see that 2 additional bindings
have been added, SOAP12 as well as REST. However I see a couple of
problems:

1) The <soap:body> element specifies a namespace even though it is a
doc/literal binding. This is disallowed explicitly by the WS-I Basic
Profile 1.1
http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Namespaces_for_soapbind_Elements

2) The bigger issue though is the endpoint addresses. I'm integrating Axis2
webapp within my larger application (EAR) and would like to use a different
webapp context than 'axis2'. However the endpoint addresses in the
generated WSDL have axis2 hard-coded in them & are of the form
http://machine:80/axis2/services/MyService

even though my Web Service is deployed at a different URL and the original
WSDL that I provided had the correct endpoint address
http://machine:80/mywebapp/services/MyService

- Junaid