When you query for the WSDL using ?wsdl, AXIS2 returns a generated WSDL and not the one you deployed.
If you want it to return the WSDL you deployed , you need to add the following to services.xml <parameter name="useOriginalWSDL"> true </parameter> However see my posting to axis-dev - which is below. There are a few issues with this - and I'll try to provide patches shortly. Mj ---------- Forwarded message ---------- From: Manoj Khangaonkar <[EMAIL PROTECTED]> Date: Feb 19, 2007 10:57 PM Subject: [AXIS2] useOriginalWSDL parameter - issues / possible solutions To: axis-dev <axis-dev@ws.apache.org> Hi all, I observed a few issues with the useOrignalWSDL parameter. Let me list them and if there is consensus I can provide the necessary patch. My understanding of the intended behavior is that if <parameter name="useOrignalWSDL"> true </parameter> is defined in services.xml, then any explicit .wsdl file that the user packaged in the services.aar is returned , when user queries for WSDL with a HTTP get such as http://localhost:8080/services/axis2/<servicename>?wsdl<http://localhost:8080/services/axis2/%3Cservicename%3E?wsdl> If useOriginalWSDL parameter is omitted or value is false, any packaged WSDL is ignored and a generated WSDL is returned. 1. So the default behaviour of the kernel is to return a generated WSDL - as if useOrginalWSDL = false. This seems a little non-intuitive. If a user explicitly deployed a WSDL file with his aar, chances are high that he wants that WSDL to be used and not the generated one. Thus the default behaviour should be useOrginalWSDL = true; in other words , if there is WSDL file in the aar, and useOrignalWSDL is not defined - then use/return the WSDL file in the aar. Defaulting to true is less work for everyone. 2. When useOrignalWSDL = false and there is an explicit WSDL in the aar, the query http://localhost:8080/services/axis2/<servicename>?wsdl<http://localhost:8080/services/axis2/%3Cservicename%3E?wsdl> returns a WSDL where the target namespace of the types section is from the explicit WSDL. Some unnecessary namespaces are declared as well. This is bug and should be fixed. 3. The code path for WSDL 20 does not check whether useOriginalWSDL is true/false 4. Lastly - is there a good use case of this parameter ? Unless there is, We could remove this parameter without losing any functionality. If the use added an explicit WSDL to the aar , then that should be used/returned and if there is no WSDL, it should be generated. If I have to add/change a parameter in services.xml and redeploy -- I can add/remove WSDL and redeploy. Mj On 2/21/07, tgb <[EMAIL PROTECTED]> wrote:
I am getting the same problem with my rpc/literal WSDL. I am using axis2 1.1.1 and the related codegen eclipse plugin v1.1.1. The generation works fine and I was able to deploy the service but it reports itself as document-literal at ?wsdl. The client I generated from the original rpc/literal/wsdl sends document-literal style messages. This all worked fine using axis 1.3 and eclipse 3.2 WTP 1.5.1 Just wondered if you ever solved the problem or if anyone else knows if the lastest nightly build fixes this issue. I've been searching but so far haven't found anyting definitive. Thanks, Tim Cox, Brian (GE Infra, Energy) wrote: > > There appears to be a problem with either the RPC WSDL code generation or > the wsdl generation. > > If I start with a valid RPC WSDL and generate the server skeleton using > the command: > > C:\1test>wsdl2java -uri BookQuoteModified.wsdl -d xmlbeans -o client -p > com.ems.client > > I receive a valid skeleton. If we go ahead and compile/deploy the > generated skeleton, and then ask for the wsdl from the service. We are > presented with a doc/literal wsdl. It seems there is an error either in > the initial codegeneration or in the service wsdl generation. Has anyone > else experienced this problem? > > Attached is a sample RPC wsdl (BookQuote2.wsdl) which ships with Axis2. > > Thanks, > > Brian > > > > <<BookQuote2.wsdl >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- View this message in context: http://www.nabble.com/RPC-WSDL---Codegen--tf2593238.html#a9092547 Sent from the Axis - User mailing list archive at Nabble.com<http://nabble.com/> . --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
