[
https://issues.apache.org/jira/browse/ODE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou updated ODE-167:
------------------------------
Fix Version/s: 1.2
This is related to our integration with Axis. We use Axis2 to publish the WSDLs
but it removes all WSDLs extensions from the coument before publishing it,
which effectively removes all the partner link type declarations.
We'll follow up with the Axis2 team.
> PartnerLinkTypes gets lost from Process WSDL upon deployment
> ------------------------------------------------------------
>
> Key: ODE-167
> URL: https://issues.apache.org/jira/browse/ODE-167
> Project: ODE
> Issue Type: Improvement
> Components: Axis2 Integration
> Affects Versions: 1.1
> Environment: Axis2 Distro
> JDK 1.5.0_11
> WinXPx64
> Reporter: Richard Taylor
> Priority: Minor
> Fix For: 1.2
>
>
> When deploying a process that includes a PartnerLinkType definition in its
> WSDL (the process'), the PartnerLinkType is lost upon deployment. For
> example say you create process foo (foo.bpel, foo.wsdl, and deploy.xml). In
> foo.wsdl you define a PartnerLinkType to allow the integration of process foo
> into future BPEL processes (recursive). After deploying the foo process,
> when you view the wsdl via http://localhost:8282/ode/services/foo?wsdl, the
> PartnerLinkType has been stripped out. This means that in order to use that
> process in another process "bar", the PartnerLinkType will need to be
> recreated for foo, even though one had already been defined. Hopefully
> this makes sense. Let me know an example is desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
