Issue 6 - Title: Make local partnerLink aliases deterministic

[Alex Yiu <alex.yiu@oracle.com>]

Issue entered
http://www.osoa.org/jira/browse/BPEL-6

Alex Yiu wrote:
>
> Danny,
>
> Thanks for raising this issue.
>
> The only under-specified part of the alias logic that I can think of 
> so far is: the numbering order.
> I think clarifying the numbering order should be the document order in 
> the process definition. That should be sufficient.
>
> Any other under-specified part of the logic?
>
> Regards,
> Alex Yiu
>
>
> Danny van der Rijn wrote:
>> TARGET: SCA C+I WS-BPEL spec, General
>>
>> DESCRIPTION: Section 2.4 lists some rules for deriving 
>> service/reference alias names for partnerLinks when there is a 
>> name-hiding in a scope.  The rules, though are non-deterministic. 
>> This will leave the algorithm that derives a component type from a 
>> BPEL file as implementation-dependent.  The goal of the algorithm is 
>> to produce a component type from a BPEL file in a deterministic way, 
>> with no external dependencies.
>>
>> PROPOSAL: none
>>
>