OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: ISSUE 43: Invalid start-from-componentType scenario in abstract


http://www.osoa.org/jira/browse/BPEL-43

 

From: Michael Rowley [mailto:michael.rowley@activevos.com]
Sent: Friday, May 15, 2009 9:22 AM
To: OASIS BPEL
Subject: [sca-bpel] NEW ISSUE: Invalid start-from-componentType scenario in abstract

 

 

DESCRIPTION:

 

The second paragraph of the specification says that the specification covers the following scenario:

 

Start from SCA Component Type. It should be possible to use WS-BPEL to implement any SCA Component Type that uses only WSDL interfaces to define services and references, possibly with some SCA specific extensions used in process definition.

 

I believe that this scenario is no longer covered.

 

PROPOSAL:

 

Change it to talk about constraining types:

 

Implement an SCA Constraining Type. It should be possible to use WS-BPEL to implement any SCA Constraining Type that uses only WSDL interfaces to define services and references, possibly with some SCA specific extensions used in process definition.

 

Michael

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]