Re: [sca-j] Issue 237: proposal

Folks,

First point is that for a resolution,
we'll need the line numbers of that modified paragraph in the latest WD
of the Spring spec.

- It is lines 592 - 594 in sca-springci-1.1-spec-WD06.doc
(section 3.0).

Second point is that we can give a normative
statement number to the new one - it should be SPR30003.

Third point is that the new paragraph
seems to just itch for a "MUST" in relation to the annotations
which are allowed/required

for a Java interface class.  The
modified statement implies an absolute requirement on a SCA Spring implementation
runtime.

Something like this? :

It is beyond the scope of this specification
to define the 

interpretation of the annotations specified
in the SCA Common 

Annotations and API Specification [ref],
except for those annotations 

that are required to be supported by
the SCA Java interface. 

The SCA runtime MUST support the SCA
annotations which are applicable

to an interface class which is referenced
by an <interface.java/> element in

the introspected component type of a
Spring application context {SPR30004] 

Other than the annotations which apply
to a Java interface referenced from an 

<interface.java/> element in the
component type, an 

implementation can ignore SCA annotations
that are present in classes 

used by the application context."

Yours, Mike

Dr Mike Edwards
 Mail Point 137, Hursley
Park

STSM
 Winchester, Hants SO21
2JN

SCA & Services
Standards
 United Kingdom

Co-Chair OASIS SCA
Assembly TC
 

IBM Software Group
  

Phone:
+44-1962 818014
  

Mobile:
+44-7802-467431 (274097)
  

e-mail:

  

 

 

From:
Anish Karmarkar <>

To:
OASIS Java <>

Date:
28/03/2011 07:55

Subject:
[sca-j] Issue 237: proposal

As discussed last week, here is the proposal for resolving
issue 237:

In section 3 Component Type of a Spring Application Context, after 

SPR30001 add:

The introspected component type MUST be a compliant SCA Java XML 

Document as defined in section 12.1 of [JAVA-CAA]. [SPR3xxxx] The 

introspected component type uses <interface.java> as the interface
type 

for the introspected services and references. Section 12.1 of [JAVA-CAA]

requires compliance with the all requirements of <interface.java>.

This will require modification of the resolution for issue 166. The 

current resolution says:

"It is beyond the scope of this specification to define the 

interpretation of the annotations specified in the SCA Common 

Annotations and API Specification [ref]. An implementation can ignore 

SCA annotations that are present in classes used by the application 

context."

This should be modified to:

"It is beyond the scope of this specification to define the 

interpretation of the annotations specified in the SCA Common 

Annotations and API Specification [ref], ***except for those annotations

that are required to be supported by the SCA Java interface***. ***Other

than the annotations required by the SCA Java interface***, an 

implementation can ignore SCA annotations that are present in classes 

used by the application context."

-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

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU