[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Spurk updated ODE-389:
--------------------------------
Attachment: CoreWS.wsdl
the auto-generated file which can be found after deployment of the testcase at
http://localhost:8585/ode/processes/CoreWS?wsdl -- the interesting part is the
undefined "null" namespace prefix in line 24
> Successfully Deployed BPEL Artifact Has an Invalid WSDL with an Undefined
> Namespace Prefix ("null")
> ---------------------------------------------------------------------------------------------------
>
> Key: ODE-389
> URL: https://issues.apache.org/jira/browse/ODE-389
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Apache Ode v1.2 deployed on an Apache Tomcat v6.0.13 web
> server under Microsoft Windows XP
> Reporter: Christian Spurk
> Attachments: CoreWS.wsdl, testcase.zip
>
>
> I have created a simple BPEL process testcase which can be deployed
> successfully in Apache Ode 1.2 but for which an invalid WSDL file is created.
> The problem is an undefined namespace prefix "null" in the generated WSDL
> file (e.g., at http://localhost:8080/ode/processes/CoreWS?wsdl):
> ...
> <wsdl:message name="string">
> <wsdl:part name="string" element="null:string"/>
> </wsdl:message>
> ...
> The prefix "null" is not defined anywhere in the WSDL document.
> Here is the directory structure of the BPEL process testcase:
> Core/
> bpel/
> core.bpel
> core.wsdl
> wsdl/
> shared.wsdl
> xsd/
> shared.xsd
> deploy.xml
> I'll attach the test files to this issue shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
