Guillaume got (1) and (2). As for (3): The integration layer provides a target EndpointReference object with each invocation of the BPEL engine. The deployment infrastructure will provide a way for associating EPRs with the endpoints implemented by the engine. The engine routes the message to the correct process by comparing the EPRs of the deployed processes to the EPR provided in the message exchange object.
-mbs On Tue, 2006-05-30 at 15:24 -0600, Lance Waterman wrote: > Thanks guys, I like this API. A couple of questions: > > 1) Not quite sure I follow how "PartnerRoleMessageExchange.replyAsync()" > works? This seems to imply the partner is dynamically changing the signature > of the service interface. > 2) MyRoleMessageExchange.setClientData() - is this used to set > "out-of-band"/partnerLink data (i.e. EPR,JMS properties, etc ... )? I can > get to this data from within a BPEL process using partnerLink in a <from> > clause - correct? > 3) I'm trying to correlate how an EPR fits into deployment. I'm assuming > that the EPR required for BpelEngine.createMessageExchange() is > produced/queried by deploying a BPEL document. The deployment API produces > an EPR for each registered BPEL <process> definition. In your API it looks > like you have a stub for deployment "BpelServer.deploy()" that returns a > QName. Is the assumption that the client translates the QName into an EPR? > > Lance > > On 5/25/06, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I've just imported the revised version of the integration API > > specified by Maciej (if somebody with the necessary karma reads this, > > Maciej's CLA has been received but he's the last one without an > > account) for review. He also brushed up the javadoc. > > > > Comments are welcome (even just to say "Good job Maciej!" :-) ). > > > > Cheers, > > > > Matthieu. > >
