The more interesting question from my Point of View is, how to actually include the Attachements, which are normally used to transport the payload on messaging like WSRM or ebXML MS.

I think there are some drafts for extending WSDL for that, but no common way to specify the schema for a secondary part.

Mit freundlichen Grüßen Bernd Eckenfels Chief Architect -- SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256 [1]mailto:b.ec...@seeburger.de - [2]http://www.seeburger.de

-----Original Message----- From: Ron Ten-Hove [mailto:Rona...@Sun.COM] Sent: Tuesday, September 09, 2003 9:04 PM To: Ugo Corda Cc: wsb...@lists.oasis-open.org Subject: Re: [wsbpel] Q: guidelines for reliability?

Ugo Corda wrote:

But what if message parts defined for reliable messaging purposes appear in the abstract WSDL? I think this kind of WSDL work has not been finalized in the two RM groups, but it's not inconceivable that the abstract WSDL could be extended with rm info.

A interesting point; should we find a way exclude such WS-{R,RM} protocol-related message parts from being used in the business process? Or, more generally, non-business related payload message parts?

-Ron

References