You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Richard Taylor (JIRA)" <ji...@apache.org> on 2007/05/04 20:43:15 UTC
[jira] Created: (ODE-130) deploying document style wsdl to Axis2
result in empty wsdl types element
deploying document style wsdl to Axis2 result 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.
[jira] Commented: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated ODE-130:
------------------------------
Fix Version/s: 1.1-incubating
Affects Version/s: 1.0-incubating
> 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
> Affects Versions: 1.0-incubating
> Environment: Windows XP x64, Tomcat 5.5.20, JDK 1.5.0_11
> Reporter: Richard Taylor
> Assigned To: Alex Boisvert
> Fix For: 1.1-incubating
>
>
> 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.
[jira] Closed: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou closed ODE-130.
-----------------------------
> 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
> Affects Versions: 1.0-incubating
> Environment: Windows XP x64, Tomcat 5.5.20, JDK 1.5.0_11
> Reporter: Richard Taylor
> Assignee: Alex Boisvert
> Fix For: 1.1-incubating
>
>
> 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.
[jira] Updated: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "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.
[jira] Resolved: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved ODE-130.
-------------------------------
Resolution: Fixed
Fixed in trunk
Sending Rakefile
Sending axis2/src/main/java/org/apache/ode/axis2/BindingContextImpl.java
Sending axis2/src/main/java/org/apache/ode/axis2/ODEServer.java
Sending axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java
Sending bpel-api/src/main/java/org/apache/ode/bpel/iapi/ProcessConf.java
Sending bpel-store/src/main/java/org/apache/ode/store/ProcessConfImpl.java
Transmitting file data ......
Committed revision 540186.
Adding axis2/src/main/java/org/apache/ode/axis2/util/Axis2UriResolver.java
Adding axis2/src/main/java/org/apache/ode/axis2/util/Axis2WSDLLocator.java
Transmitting file data ..
Committed revision 540187.
> 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
> Affects Versions: 1.0-incubating
> Environment: Windows XP x64, Tomcat 5.5.20, JDK 1.5.0_11
> Reporter: Richard Taylor
> Assigned To: Alex Boisvert
> Fix For: 1.1-incubating
>
>
> 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.
[jira] Assigned: (ODE-130) Deploying document style wsdl to Axis2
results in empty wsdl types element
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert reassigned ODE-130:
---------------------------------
Assignee: Alex Boisvert
> 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
> Affects Versions: 1.0-incubating
> Environment: Windows XP x64, Tomcat 5.5.20, JDK 1.5.0_11
> Reporter: Richard Taylor
> Assigned To: Alex Boisvert
> Fix For: 1.1-incubating
>
>
> 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.