[Users] PartnerLink and interface in the petals-se-orchestra

[Jérémie Doucy]

Hello,
At EADS we develop the WebLab platform (http://weblab-project.org) which is an Open platform for processing multimedia documents.
So we choose to use PEtALS as ESB.
We need complex services chains so I tried all the petals-se-orchestra versions (release and trunk) since its first release.

So in our platform we provide standard WSDL and XSD files. That means that we have a lot of implementations for the same service interface.

But, in bpel, each partner link is linked to an interface, and only an interface (not a service or an enpoint address). So when I create a chain using BPEL I'm not able to precise the real serviceName or endpoint to use, the only thing I can precise is the interface. And so when I use an invoke BPEL operation, the NMR choose an implementation.

I need to choose the service Name and eventually the endpoint name by myself (more or less dynamically). So to do this, I patch the petals-se-orchestra and add an XML file to the jbi.xml attributes which links each partner link (by name) to a service definition (using ws-addressing). I did this because orchestra steel not implement the partnerlink dynamic affectation using the assign operation.

So I have two questions : 

Do you know if orchestra will implement the assign operation on a partnerlink ?

If not, could I have the commit rights on the svn to officially patch the se-orchestra ?

Thanks in advance.

------------------------
Information Processing Competence Center (IPCC)
EADS Defence and Security Systems
http://weblab-project.org




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=414#414

-------------------- m2f --------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110316/ad495547/attachment.htm>