[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue 194: Faults for uninitialized partnerLinks
> An uninitialized partner link (partner role) used in an invoke activity > should lead to a BPEL standard fault. What would that standard fault be? That's the point of this issue, to define the standard fault. > I was under the impression that Issue > 139 is supposed to cover this. It easily could have but I figured that 139 is carrying enough on its shoulders and the problem in 194 can be solved without having to resolve 139. > Maybe I am not getting the point but the scenario about an uninitialized > partner link (my role) is not clear to me. An assign from my role must > always produce a valid service ref. Other activities (like receive) should > not be affected at all. The scenario is that someone creates a partnerLink. The deployment administrator does not initialize the partnerRole in the partnerLink. The very first time the partnerLink is ever used in the process is for an Invoke. Since no value was ever placed in the partnerRole there is no EPR for the invoke to target and hence an error occurs. But what error? That's what the issue is trying to define. Yaron Dieter Koenig1 wrote: > An uninitialized partner link (partner role) used in an invoke activity > should lead to a BPEL standard fault. I was under the impression that Issue > 139 is supposed to cover this. > > Maybe I am not getting the point but the scenario about an uninitialized > partner link (my role) is not clear to me. An assign from my role must > always produce a valid service ref. Other activities (like receive) should > not be affected at all. > > Kind Regards > DK >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]