[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640150#action_12640150
]
Christian Spurk commented on ODE-389:
-------------------------------------
@Tammo, thanks for looking into this!
Maybe I was not clear enough: the files from the testcase itself should be ok
as I have manually created all of them. The problem is the WSDL document which
is auto-generated by Ode when I deploy the testcase as a BPEL process, i.e.,
when I put the "Core" directory into the $TOMCAT/webapps/ode/WEB-INF/processes
directory. The deployment works without any warnings or error messages but the
WSDL file which is generated for the BPEL process is not valid. I'll attach the
generated WSDL document from which I have copied the WSDL message snippet above
in a minute. Hopefully the problem will be a bit clearer then.
> 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.
