[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ISSUE-29: Specification inconsistent - states that callbacks can be used for both local and remote services and elsewhere says only for remote service interfaces
Von: Mark Combellack [mailto:mcombellack@avaya.com] Gesendet: Donnerstag, 21. Februar 2008 16:06 An: OASIS Java Betreff: [sca-j] NEW ISSUE: Specification inconsistent - states that callbacks can be used for both local and remote services and elsewhere says only for remote service interfaces RAISER:
Mark Combellack TARGET:
Java Common Annotations and APIs Specification DESCRIPTION: The Java Common Annotations and APIs
Specification is inconsistent as it states that callbacks can be used for both
local and remote services and elsewhere says only for remote
services. Line numbers are based on version
1.1 of the Working Draft dated 26 September 2007 In the following, line 356 states
that “Callbacks may be used for both remotable and local
services” 356
Callbacks may be used for both remotable and local services. Either both
interfaces of a 357
bidirectional service must be remotable, or both must be local. It is
illegal to mix the two. There 358
are two basic forms of callbacks: stateless callbacks and stateful
callbacks. In the following, line 359 states
that “A callback interface is declared by using the @Callback annotation on a
remotable service interface” This implies that @Callback can only be used on
@Remotable service interfaces. 359
A callback interface is declared by using the @Callback annotation on a
remotable service 360
interface, which takes the Java Class object of the interface as a parameter.
The annotation may 361
also be applied to a method or to a field of an implementation, which is used in
order to have a 362
callback injected, as explained in the next section.
PROPOSAL: Remove the word remotable in line
359 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]