RE: [wsbpel] Input and Input/output

["Ugo Corda" <UCorda@SeeBeyond.com>]

The latest recommendations from the WSD Patterns Task Force are at http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/meps-vs-iops/recommendations_clean.htm . I don't think this work has been finalized by the WSD group yet.

Ugo

> -----Original Message-----
> From: Satish Thatte [mailto:satisht@microsoft.com]
> Sent: Friday, September 05, 2003 5:50 PM
> To: ygoland@bea.com; edwink@collaxa.com; Wsbpel@Lists. Oasis-Open. Org
> (E-mail)
> Subject: RE: [wsbpel] Input and Input/output
> 
> 
> It would be good to investigate where WSDL 1.2 is in this respect --
> that would give us useful guidance in what we decide to do.
> 
> -----Original Message-----
> From: Yaron Goland [mailto:ygoland@bea.com] 
> Sent: Tuesday, August 26, 2003 11:19 AM
> To: edwink@collaxa.com; 'Wsbpel@Lists. Oasis-Open. Org (E-mail)'
> Subject: RE: [wsbpel] Input and Input/output
> 
> If someone where to feed a BPEL engine a BPEL process definition that
> included a WSDL definition that included a output or output/input
> operation
> the BPEL engine would reject the process.
> 
> The reason being, as you point out, that output and 
> output/input aren't
> needed by BPEL as they are handled implicitly by 
> partnerLinkType in the
> manner you describe.
> 
> However, the WSDL 1.1 standard does include output and output/input
> operations and a user familiar with the standard would 
> reasonably expect
> that BPEL would support these operation types. Given that we do not
> (which,
> btw, not only makes sense but also is consistent with 
> industry practice)
> it
> would seem reasonable to have some text in the standard which 
> points the
> situation out and explains it.
> 
> What I'm trying to figure out is if that language is already 
> in the spec
> or
> if we need to open an issue to have it added.
> 
> 	Thanks,
> 
> 		Yaron
> 
> > -----Original Message-----
> > From: Edwin Khodabakchian [mailto:edwink@collaxa.com]
> > Sent: Monday, August 25, 2003 8:50 AM
> > To: ygoland@bea.com; 'Wsbpel@Lists. Oasis-Open. Org (E-mail)'
> > Subject: RE: [wsbpel] Input and Input/output
> >
> >
> > Hi Yaron,
> >
> > The formalism for output and output/input is based on
> > partnerLinkTypes. A
> > receive on a partnerLink is equivalent to the output operation.
> > Receive/reply is equivalent to a output/input.
> >
> > This is an area that is not easy to learn so we should try to
> > have only one
> > formalism: output or partnerLinks.
> >
> > How is dynamic binding implemented using output? Meaning in
> > the case of an
> > output operation is the binding provided by the service that
> > performes the
> > callback or the service that provides the callback?
> >
> > Thank you,
> > Edwin
> >
> > > -----Original Message-----
> > > From: Yaron Goland [mailto:ygoland@bea.com]
> > > Sent: Monday, August 25, 2003 8:39 AM
> > > To: Wsbpel@Lists. Oasis-Open. Org (E-mail)
> > > Subject: [wsbpel] Input and Input/output
> > >
> > > BPEL only supports input and input/output WSDL operations. It
> > > does not support output and output/input. This makes sense as
> > > the vast majority of Web Service stacks don't have support
> > > for output and output/input either. However this is something
> > > that needs to be expressed in the specification. I thought
> > > text on the subject had been added to the spec but I just
> > > looked for it and couldn't find it. Can anyone point me to
> > > the text or do we need to open an issue?
> > >
> > > 	Thanks,
> > > 		Yaron
> > >
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org
> 
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.