[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-bpel] NEW ISSUE: Title: The algorithm for deciding whethera partnerLink is a service or a reference needs to be deterministic
Hi, Danny, The way that I read that section is: the logic there is quite deterministic already: If a partnerLink can be determined as a service, Let me give you an example. If a partnerLink is used in both invoke and receive activities without any logical ordering enforced in the process definition, it will go into the reference case. Because, the static analysis CANNOT determine the partnerLink is a service. My thought is: if different implementation come out a different componentType definition after static analysis of the same process, it sounds to me that it is more like a bug in an implementation, not the case of the spec being unclear. (unless you can give me a concrete example of our existing rules are not sufficient) And, I think if users do not want to rely on static analysis of a BPEL process to calculate the componentType, it may be a better idea to ask users to supply an explicit componentType artifact. (That is an issue raised by Anish.) Thanks! Regards, Alex Yiu Danny van der Rijn wrote: 46F2E66C.5010000@tibco.com" type="cite">TARGET: SCA C+I WS-BPEL spec, General |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]