ISSUE-114: Spring CI runtime behaviour when annotation rules are violated

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

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

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

Simon Nash ---12/08/2008 11:25:34 AM---Resending this email because the first attempt omitted "NEW ISSUE" from the subject line.

From:	Simon Nash <oasis@cjnash.com>
To:	sca-j@lists.oasis-open.org
Date:	12/08/2008 11:25 AM
Subject:	[sca-j] NEW ISSUE: Spring CI runtime behaviour when annotation rules are violated

---

Resending this email because the first attempt omitted "NEW ISSUE"
from the subject line.

   Simon

TARGET: Spring Component Implementation specification

DESCRIPTION: Spring CI runtime behaviour when annotation rules are violated

The definitions of various SCA annotations specify rules and constraints
that go beyond those syntactic rules that the Java compiler can enforce.

The Spring Component Implementation specification needs to specify what
happens if these annotation rules are violated.

PROPOSAL:

If a Spring component implementation contains annotations that violate
the rules in the Java Common Annotations and APIs specification,
the SCA runtime MUST NOT deploy any component using that implementation.

If a Java interface for a service or reference contains annotations that
violate the rules in the Java Common Annotations and APIs specification,
the SCA runtime MUST NOT deploy any Spring component using that interface.


---------------------------------------------------------------------
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