ISSUE-164: Spring C&I SCA extension element does not provide fullfunctionality possible in an SCA CT

[David Booz <booz@us.ibm.com>]

http://www.osoa.org/jira/browse/JAVA-164

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Anish Karmarkar ---05/22/2009 01:39:21 AM---Title: Spring C&I SCA extension element does not provide full functionality possible in a SCA CT

From:	Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:	OASIS Java <sca-j@lists.oasis-open.org>
Date:	05/22/2009 01:39 AM
Subject:	[sca-j] NEW ISSUE: Spring C&I SCA extension element does not provide full functionality possible in an SCA CT

---

Title: Spring C&I SCA extension element does not provide full 
functionality possible in a SCA CT

Target: Spring C&I

Description:
The Spring C&I spec provides it's own version of 
sca:service/reference/property extension elements that can be used in an 
app context. This allows one to explicitly specify the component type 
associated with the context. But these capabilities are severely 
constrained. For example, one cannot specify intents, policySets or 
bindings.

Proposal:
One possible solution is to reuse the elements 
(service/reference/property) that are already defined in the main SCA NS 
to replace the spring specific ones.

-Anish
--

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php