← Prev in month
← Prev in thread
Next in thread →
Next in month →
ISSUE-172: Java CAA spec - Incorrect use of RFC2119 keywords
http://www.osoa.org/jira/browse/JAVA-172 Dave Booz STSM, BPM and SCA Architecture Co-Chair OASIS SCA-Policy TC and SCA-J TC "Distributed objects first, then world hunger" Poughkeepsie, NY (845)-435-6093 or 8-295-6093 e-mail: David Booz---07/20/2009 04:06:14 PM---TARGET: Java CAA specification CD03/PR01 [1] DESCRIPTION: From: David Booz/Poughkeepsie/IBM@IBMUS To: Date: 07/20/2009 04:06 PM Subject: [sca-j] NEW ISSUE: Java CAA spec - Incorrect use of RFC2119 keywords TARGET: Java CAA specification CD03/PR01 [1] DESCRIPTION: There are several places where RFC2119 keywords are misused: a) The @AllowsPassByReference annotation MAY be placed on an individual method of a remotable service implementation, on a service implementation class, or on an individual reference for a remotable service. When applied to a reference, it MAY appear anywhere that the @Remotable annotation MAY appear. It MUST NOT appear anywhere else. [JCA90052] b) A method annotated with @Destroy MAY have any access modifier and MUST have a void return type and no arguments. [JCA90004] c) A method marked with the @Init annotation MAY have any access modifier and MUST have a void return type and no arguments.[JCA90008] d) For SCA reference interfaces defined using interface.java, the Java interface MAY contain the additional client-side asynchronous polling and callback methods defined by JAX-WS. [JCA100007] e) Section 12 has several uses of unlabelled RFC keywords. Was that intentional? Lines 2338, 2341, 2344, 2345, 2354, 2356, 2358, 2360, 2362 PROPOSAL: a) Replace JCA90052 with the following: The @AllowsPassByReference annotation MUST only be placed on the following locations; an individual method of a remotable service implementation, on a service implementation class, or on an individual reference for a remotable service. When applied to a reference, it MUST NOT appear anywhere that the @Remotable annotation MUST NOT appear. [JCA90052] b) Replace JCA90004 with the following: A method annotated with @Destroy can have any access modifier and MUST have a void return type and no arguments.[JCA90004] c) Replace JCA90008 with the following: A method marked with the @Init annotation can have any access modifier and MUST have a void return type and no arguments.[JCA90008] d) Replace JCA100007 with the following: For SCA reference interfaces defined using interface.java, the Java interface can contain the additional client-side asynchronous polling and callback methods defined by JAX-WS. [1] http://docs.oasis-open.org/opencsa/sca-j/sca-javacaa-1.1-spec-cd03.pdf Dave Booz STSM, BPM and SCA Architecture Co-Chair OASIS SCA-Policy TC and SCA-J TC "Distributed objects first, then world hunger" Poughkeepsie, NY (845)-435-6093 or 8-295-6093 e-mail:
← Prev in month
← Prev in thread
Next in thread →
Next in month →