Re: [sca-bpel] Issue 2 - Does the spec allow a componentType sidefile?

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

+1 to Michael's suggested usage of the componentType side file.


Regards,
Alex Yiu



Michael Rowley wrote:

2E22E42D2E71B845B67F093A02B962DB012D41AC@repbex01.amer.bea.com" type="cite">

One thing a side file might be used for is to override the default
algorithm that decides on which partnerlinks are services and which are
references.  Do you agree?  If so, I think the side file would have to
have a way of pointing from a service or reference declaration to a
partnerlink.

Michael

-----Original Message-----
From: Anish Karmarkar [mailto:Anish.Karmarkar@oracle.com] 
Sent: Thursday, October 18, 2007 1:58 AM
To: OASIS BPEL
Subject: Re: [sca-bpel] Issue 2 - Does the spec allow a componentType
side file?

Proposed resolution:

In section 2, line 194 add --
It is also possible to have a component type file that is associated 
with the BPEL component implementation. When such a component type file 
is present, as specified in [SCA-Assembly], it provides component type 
information in addition to what is found by introspection.


Do we need to define compatibility between what is found by 
introspection and what is available in the side file?

Comments?

-Anish
--

Alex Yiu wrote:
  

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



Anish Karmarkar wrote:
    

Title: Does the spec allow a componentType side file

Target: BPEL C&I spec

Description: The spec does not say whether a componentType side file 
is allowed. If it is allowed then it should override the default
      

rules 
  

specified in the spec.

Proposal:
<none>