Re: [sca-j] [ISSUE 157] Section 10.13 on @OneWay requires a normativestatement - Updated Proposal 2

[Simon Nash <oasis@cjnash.com>]

As dicussed on Friday's call, I would like to propose a small change
to section 3.5 to make it non-normative.  The reason for this change
is that the base definition of compatibility in the Assembly spec is
also non-normative, providing a definition that is used in other
normative statements covering wiring, promotion, etc.  The text in
section 3.5 is written as a supplement to the non-normative Assembly
definition of compatibility, not as a supplement to the normative
statements in the Assembly spec relating to the situations where
compatibility applies (promotion, wiring, etc.)  As such this text
should be non-normative to match the base text in Assembly to which
it applies.

Here is a suggested rewording of the text for this section.

3.5 Compatibility of Java Interfaces

The SCA Assembly Model specification [ASSEMBLY] defines a number of
criteria that need to be satisfied in order for two interfaces
to be compatible or have a compatible superset or subset relationship.
If these interfaces are both Java interfaces, compatibility also
means that every method that is present in both interfaces is defined
consistently in both interfaces with respect to the @OneWay annotation,
that is, the annotation is either present in both interfaces or absent
in both interfaces.

   Simon

Mike Edwards wrote:
> 
> Folks,
> 
> Following the discussion on the list, here is an updated proposal for 
> Issue 157:
> 
> All line numbers refer to the PDFs of the Public Review drafts of the 
> specifications.
> 
> 
> Replace lines 1731 - 1733 of Java CAA with the following normative 
> statements:
> 
> When a method of a Java interface is annotated with @OneWay, the SCA 
> runtime MUST ensure that all
> invocations of that method are executed in a non-blocking fashion, as  
> described in the section on Asynchronous Programming.
> [JCA90052]
> 
> Methods of Java classes MUST NOT be annotated with the @OneWay 
> annotation. [JCA90053]
> ----------------------------------------------------------
> 
> Add the following new section after line 325 of Java CAA:
> 
>  3.5 Compatibility of Java Interfaces
> 
>   The SCA Assembly Model specification [ASSEMBLY] defines a number of 
> criteria that need to be satisfied in order for two interfaces
>   to be compatible or have a compatible superset or subset relationship. 
>   If these interfaces are both Java interfaces, compatibility also
>  means that every method that is present in both interfaces MUST be 
> defined consistently in both interfaces with respect to the @OneWay 
> annotation,
>   that is, the annotation is either present in both interfaces or absent 
> in both interfaces. [JCA30009]
> -----------------------------------------------------------
> 
> Change lines 467 - 469 of the Java CAA to read:
> 
> 
> A method with a void return type and which has no declared exceptions 
> can be marked with a */@OneWay /*annotation.
> This means that the method is non-blocking and communication with the 
> service provider can use a binding that buffers
> the request and sends it at some later time.
> ------------------------------------------------
> 
> Change lines 173 - 176 of the Java C&I spec to read:
> 
> Service operations defined by a Java interface can use the @OneWay 
> annotation to declare that the
> SCA runtime needs to honor non-blocking semantics as defined by the SCA 
> Assembly Model Specification
> [ASSEMBLY] when a client invokes the service operation.
> ------------------------------------------------------------
> 
> 
> 
> 
> Yours,  Mike.
> 
> Strategist - Emerging Technologies, SCA & SDO.
> Co Chair OASIS SCA Assembly TC.
> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
> Email:  mike_edwards@uk.ibm.com
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> /
> /
> 
> /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/
> 
> 
> 
> 
> 
>