[jira] Updated: (ODE-130) Deploying document style wsdl to Axis2 results in empty wsdl types element

["Richard Taylor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Taylor updated ODE-130:
-------------------------------

    Summary: Deploying document style wsdl to Axis2 results in empty wsdl types element  (was: deploying document style wsdl to Axis2 result in empty wsdl types element)

It appears that although the generated WSDL is missing the proper schema type definitions, the process still works OK.  So if you know the proper SOAP message to send to the process, it will still execute despite the bad generated WSDL.  

> Deploying document style wsdl to Axis2 results in empty wsdl types element
> --------------------------------------------------------------------------
>
>                 Key: ODE-130
>                 URL: https://issues.apache.org/jira/browse/ODE-130
>             Project: Ode
>          Issue Type: Bug
>          Components: Axis2 Integration
>         Environment: Windows XP x64, Tomcat 5.5.20, JDK 1.5.0_11
>            Reporter: Richard Taylor
>
> When deploying a process and specifying a soap binding style of "document" in the process' WSDL, the WSDL that Axis2 generates after deployment has an empty <wsdl:types> element.  In other words all schema / type information is lost from the WSDL.  The WSDL is not correct at that point which prevents the use of any tools / clients that are based on the generated WSDL.
> This simplest way to reproduce this is to deploy the DynPartner Axis2 example that comes with Ode, then view the WSDL that is return when hitting the URL http://localhost:8080/ode/services/DynMainService?wsdl.  You will notice that the types section is empty.  The schema has been lost.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.