ISSUE-115: Runtime behaviour when annotation rules are violated

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

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

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 10:25:52 AM---TARGET: Java Component Implementation specification DESCRIPTION: Runtime behaviour when annotation r

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

---

TARGET: Java Component Implementation specification

DESCRIPTION: 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 Java Component Implementation specification needs to specify what
happens if these annotation rules are violated.

PROPOSAL:

If a Java 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 Java 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