Ah, yes, I think it is possible to assign the output of a receive to the same variable twice, granted they represent the xsd type.
On Sun, Aug 22, 2010 at 01:54, Łukasz Budnik <[email protected]>wrote: > Hi Antoine, > > Yes I know that if 2 Web Services have the same interface, the > messages can be reused. > > But I'm thinking of something else: > > <invoke partnerLink="supplierPartnerLink" operation="checkIfInStock" ... > outputVariable="normalisedMessage" /> > > <invoke partnerLink="shippingPartnerLink" operation="shipOrder" ... > outputVariable="normalisedMessage" /> > > In the example above there are 2 different partner links, 2 different > operations, and 2 different return types, but they are both assigned > to outputVariable="normalisedMessage". > > Is it possible to assign the results to a common variable. Something > like a normalised message concept in ESB world. > > thanks, > Łukasz > > On 21 August 2010 18:41, Antoine Toulme <[email protected]> wrote: > > Not sure I follow - you can use a message that is reused in your > operations > > of your wsdl. So potentially you can reuse the same message across > invokes. > > The reuse happens in the WSDL, not the BPEL. > > > > On Sat, Aug 21, 2010 at 06:40, Łukasz Budnik <[email protected] > >wrote: > > > >> All, > >> > >> I'm thinking about creating something like an ESB in WS-BPEL. I want > >> to have a NormalisedMessage (NM). > >> > >> Is it possible to create one message which would be used in all > >> invokes across the whole business process? > >> > >> E.g., > >> > >> <invoke partnerLink="partnerLink1" operation="op1" ... > >> outputVariable="normalisedMessage" /> > >> > >> <invoke partnerLink="partnerLink2" operation="op123" ... > >> outputVariable="normalisedMessage" /> > >> > >> thanks, > >> Łukasz > >> > >> thanks, > >> Łukasz > >> > > >
