axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishnamoorthy J (HCL Financial Services)" <>
Subject RE: Axis 2 v1.1.1: disabling auto generated WSDL file
Date Thu, 22 Mar 2007 03:04:53 GMT

I got it to work. It's in the mailing list with subject "how to get
custom WSDL during runtime instead of generated WSDLin Axis 2"


May be the parameter name "useOriginalwsdl" is case sensitive.
<parameter name="useOriginalwsdl">true</parameter>


Also, the service name in the service.xml file, the service name in the
WSDL file and the WSDL file name should be same. Then only your own wsdl
file will be displayed.


- Krishna



From: Vibhor_Sharma [] 
Sent: Wednesday, March 21, 2007 10:19 PM
Subject: RE: Axis 2 v1.1.1: disabling auto generated WSDL file


Does it really work?

I tried setting the param in my service.xml file and still see the one
generated by axis engine? I do not see my own WSDL.



<service name="CertifyChannel">

<module ref="logging"/>


<module ref="rampart"/>


<parameter name="useOriginalWSDL">true</parameter>


Is there some other place I have to substitute this value??





From: D P [] 
Sent: Wednesday, March 21, 2007 12:01 PM
Subject: Axis 2 v1.1.1: disabling auto generated WSDL file


Hello all,
When a client queries the service wsdl at http://../../serviceName?wsdl,
I would like the service to return the wsdl which I packaged in the .aar
file, _not_ an auto generated wsdl.  I came across a possible solution

1.  It appears though there are some issues with the solution.  Does
anyone know if this works for sure? 

2.  After implementing the solution in my services.xml file, i noticed 2
a.) i've refactored out some schema into an xsd file, and import it to
multiple wsdls.  A copy of the xsd file is packaged with each wsdl and
the code to import the xsd uses schemaLocation=" foo.xsd".  But when I
look at the wsdl file at http://../../serviceName?wsdl, the
schemaLocation element value is now
schemaLocation="serviceName?xsd=xsd0".  Why is this happening?

b) When I look at the wsdl file at http://../../serviceName?wsdl, i
notice that wsdl:portType/wsdl:operation/wsdl:input and
wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
original wsdl I packaged with the .aar does not. Why is this happening? 

Any feedback would be appreciated.


The contents of this e-mail and any attachment(s) are confidential and intended for the named
recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or
opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of
HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and
/ or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited.
If you have 
received this email in error please delete it and notify the sender immediately. Before opening
any mail and 
attachments please check them for viruses and defect.

View raw message