RE: [sca-bpel] Issue 17 - Allow Component Type side file to override defaults for service/reference

Changed the subject to reflect the relevant issue 
...

  

  
  From: Michael Rowley [mailto:] 
  
Sent: Thursday, Feb 21, 2008 12:11 PM
To: OASIS 
  BPEL
Subject: RE: [sca-bpel] Issue 2 - Does the spec allow a 
  componentType side file?

  

  

  
 

  
Note that I’ve just submitted this 
  new issue to the Assembly TC, suggesting the introduction of 
  service/@implementationRef and reference/@implementaitonRef in component 
  types.

  
 

  
I would suggest that, as part of 
  the resolution of issue 2, the BPEL TC describe the contents of the 
  @implementationRef attribute as follows:

  
 

  
The @implementationRef attribute 
  MUST contain a valid XPath 1.0 expression, which when executed on a BPEL 
  process returns exactly one <partnerLink> element.  The partnerLink 
  thus identified will be considered to correspond to the service or reference 
  that contained the @implementationRef attribute.  If a service or 
  reference does not have an @implementationRef attribute, then it will act as 
  if it had @implementationRef=”//partnerLink[@name=’$name’]”, where $name is 
  the value of the @name attribute of that service or 
  reference.

  
 

  
 

  
Michael