[sca-j] ISSUE 27 - Security Annotations in generated Component Type -proposal

Here is the proposal for issue 27: http://www.osoa.org/jira/browse/JAVA-27. 

The highlights of the proposal:

1. Instead of defining SCA security implementation policy annotations, point to JSR 250  security annotations

2. Not generating componentTypes for the above annotations, due to two major reasons: 

some of the annotations can apply onto the methods level, while component type definition does not have operational level any more. 

if we did generate the information into component type, we also need to generate the policysets to apply the policy...

3. Also added are the other annotations that is missing from section 8, related to 10.3 Application intent annotations: 

@Authentication

@Confidentiality

@Integrity

@Intent

@PolicySets

@Qualifier

@Requires

All the changes are under  8.2, 8.5, 8.15, 8.19, 8.22, 8.25, 10.6.2, 10.6.2.1.

(See attached file: sca-javacaa-1.1-spec-cd01-rev4a-Issue27.doc)(See attached file: sca-javacaa-1.1-spec-cd01-rev4a-Issue27.pdf)

Thanks Dave for the review and comments earlier.

Regards,

Yang Lei

WebSphere SCA Feature Pack Development -- SCA Architect

Phone: (919) 543 8887  T/L  441-8887

e-mail: 

SCA Feature Pack:  http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome

RTP Technical Vitality: http://swgcomm.bluehost.ibm.com/siteFiles/labs.html?location=SEUS&type=cluster

WebSphere Lab Advocate for Royal Bank of Scotland

sca-javacaa-1.1-spec-cd01-rev4a-Issue27.doc

sca-javacaa-1.1-spec-cd01-rev4a-Issue27.pdf