[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] wsbpel 3/30/2006: Extensibility Reference (Section 5.3)
Hi, Monica and Danny, Section 8.3 is not talking BPEL extensibility per see. It is talking how BPEL makes use of XPath extension function. But, it does not hurt to add a reference to Section 5.3 in Section 8.3. On the other hand, I think we may also want to explicit call out that in Section 8.3: * WS-BPEL processor may make XPath extension function of other NS available. * The <extension> declaration does NOT cover those XPath extension functions and they must be always understood by WS-BPEL processor. If unrecognized XPath function is used and if it is detected by static analysis, the process defintion must be rejected. * The XPath extension, as always required by XPath semantics, MUST not perform any side-effect operation visible to the WS-BPEL process. The last bullet is important to add because a lot of XPath users presume otherwise. In the javadoc of (javax) XPath function object, similar no-side-effect caution is called out as well. (Since the above are already mentioned in other parts of BPEL spec or implied by other specifications, I don't consider a normative change. An Action Item would be good enough, IMHO). Regards, Alex Yiu Danny van der Rijn wrote: An interesting thought. 5.3 is currently about how to extend BPEL, not how BPEL extends XPath (or WSDL). I could see having it do that, but otoh, it's not inconsistent or incomplete as it is. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]