OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: NEW ISSUE: MAY clauses in JCA90029 and JCA90033


TARGET: Java Common Annotations and APIs

DESCRIPTION: MAY clauses in JCA90029 and JCA90033

The meaning of the MAY clauses in JCA90029 and JCA90033 is
unclear.  The clauses both say that a reference MAY continue
to work after its target service has been changed.  If it does
not continue to work, is any behaviour (e.g., exiting the JVM)
acceptable?

The sentences following JCA90029 and JCA90033 (currently marked
as non-normative) imply that a completely unconstrained failure
mode was not intended.  They seem to imply that an exception
MUST be thrown, and the type of exception is implementation
dependent.

I believe a more accurate way to state the intention of
JCA90029 and JCA90033 would be:

If the target service....is changed, the reference MUST either
continue to work or throw an exception when it is invoked,
depending on the runtime and the type of change that was made.

PROPOSAL:

Change JCA90029 to:

If the target service of the reference is changed, the reference
MUST either continue to work or throw an exception when it is invoked,
depending on the runtime and the type of change that was made.

Change JCA90033 to:

If the target service of a ServiceReference is changed, the reference
MUST either continue to work or throw an exception when it is invoked,
depending on the runtime and the type of change that was made.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]