You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2008/10/16 14:14:44 UTC
[jira] Commented: (ODE-389) Successfully Deployed BPEL Artifact Has
an Invalid WSDL with an Undefined Namespace Prefix ("null")
[ https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640149#action_12640149 ]
Tammo van Lessen commented on ODE-389:
--------------------------------------
I can't find any issue with the testcase.
The only wsdl message defined in shared.wsdl looks like this:
<wsdl:message name="string">
<wsdl:part name="string" element="sns:string" />
</wsdl:message>
and sns is properly bound to http://www.example.com/xsd/shared.xsd in the root element.
> 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: 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.