[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Q: guidelines for reliability?
Martin Chapman wrote:This is a general problem regardless. We have to wait until deployment time to ensure that compatible bindings are selected.. Your suggestion about QoS data is interesting. Should BPEL messaging activities be able to include some general QoS information (for instance, that an encrypted transport be used for sensitive transactions). Such things are arguably part of the business process, as opposed to deployment descriptor. "Abstract" QoS requirements from the process would help the deployer to select the right bindings to achieve the QoS desired by the business process designer without necessarily getting into messy technical details. Something like: <receive partnerLink = "buyer"where portOptions is an optional attribute containing a list of QoS related tokens that are suitably abstract. These could be used by the deployer when selecting or creating the appropriate bindings for the abstract operation "acceptPayment". This still wouldn't help the interoperability problem -- two deployers for two different engines that must interoperate must "exchange notes" to assure compatible bindings are chosen. This starts to become a very CPA-like exercise. -Ron |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]