You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthieu Riou (JIRA)" <ji...@apache.org> on 2007/05/05 00:17:15 UTC
[jira] Commented: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
[ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493811 ]
Matthieu Riou commented on ODE-130:
-----------------------------------
ODE only uses the WSDL document you're providing, it doesn't care at all about what Axis2 is publishing. So it's only a problem in that publishing, the engine isn't impacted,
> 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.