Hi Anish,
1) Adding "if present" wouldn't hurt anything, so I'm fine with adding that
to the proposal for both new normative statements.
2) yes - that's a typo
So with these two changes we get:
The value of the name attribute of the @WebService annotation, if present,
MUST be used to define the name of an SCA service when there is no @Service
annotation present in the SCA component implementation. [JCA1000xx]
The value of the name attribute of the @WebService annotation, if present,
MUST be used to define the name of an SCA service when the @Service
annotation is present without the names attribute and indicates that the
Java interface or class annotated with the @WebService annotation defines
an SCA service interface. [ JCA1000xx]
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:
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Anish Karmarkar <> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|10/18/2010 01:40 AM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: Fw: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
On 10/13/2010 2:27 PM, David Booz wrote:
>
> Getting back on the list now. Bryan and I have been tweaking the
proposed
> wording for Java-212, notably the normative text in the CAA spec. Here's
> the latest proposal that would replace JCA100028.
>
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when there is no @Service annotation
> present in the SCA component implementation. [JCA1000xx]
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when the @Service annotation is present
> without the names attribute and indicates that the Java interface or
class
> annotated with the @WebService annotation defines an SCA service
interface.
> [ JCA1000xx]
>
> If you read the full email chain you'll see how we got here. Any
opinions?
>
I like separating them as two normative statements as drafted above.
Easier to read/parse. Two comments:
1) Don't we need a "if present" after "... of the @Webservice annotation".
2) nit: I assume there is an "of" after "... MUST be used to define the
name"
-Anish
--
> 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:
> ----- Forwarded by David Booz/Poughkeepsie/IBM on 10/13/2010 05:22 PM
-----
> |------------>
> | From: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Bryan Aupperle/Raleigh/IBM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |David Booz/Poughkeepsie/IBM@IBMUS
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |10/13/2010 02:48 PM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Re: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
> I generally prefer normative statements that are a single sentence, but
the
> second option is easier to read. Either is an improvement over my tweak.
>
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> WW Center of Excellence for Enterprise Systems& Banking Center of
> Excellence Application Integration Architect
> Master Inventor
>
> Research Triangle Park, NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address:
>
>
> |------------>
> | From: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |David Booz/Poughkeepsie/IBM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Bryan Aupperle/Raleigh/IBM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |10/13/2010 02:31 PM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Re: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
> Yours is better than mine...
>
> How about another tweak:
>
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when there is no @Service annotation
> present in the SCA component implementation or when the @Service
annotation
> is present without the names attribute and indicates that the Java
> interface or class annotated with the @WebService annotation defines an
SCA
> service interface.
>
> or this:
>
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when there is no @Service annotation
> present in the SCA component implementation.
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when the @Service annotation is present
> without the names attribute and indicates that the Java interface or
class
> annotated with the @WebService annotation defines an SCA service
interface.
>
> 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:
>
>
>
> |------------>
> | From: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Bryan Aupperle/Raleigh/IBM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |David Booz/Poughkeepsie/IBM@IBMUS
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |10/13/2010 02:14 PM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Re: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
> Slight modification, but overall I like it.
>
> The value of the name attribute of the @WebService annotation MUST be
used
> to define the name an SCA service when there is no @Service annotation
> present in the SCA component implementation or when the @Service
annotation
> is present and indicates that the Java interface or class annotated with
> the @WebService annotation defines an SCA service but the names attribute
> of the @Service annotation is not specified.
>
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> WW Center of Excellence for Enterprise Systems& Banking Center of
> Excellence Application Integration Architect
> Master Inventor
>
> Research Triangle Park, NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address:
>
>
>
> |------------>
> | From: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |David Booz/Poughkeepsie/IBM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Bryan Aupperle/Raleigh/IBM@IBMUS
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |10/13/2010 02:03 PM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Re: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
> Here's the two normative statements in CAA.
>
> The name of a service with an interface defined by a Java interface or
> class annotated with the @WebService annotation with its name attribute
set
> MUST be the value of the name attribute of the annotation. [JCA100023]
> If a service is named by both name attribute of a @Service annotation and
> the name attribute of a @WebService annotation and the name attribute
> values differ, an SCA Runtime MUST use the value from the name attribute
of
> the @Service annotation. [JCA100028]
>
> I think what we're after is something like this:
>
> The value of the name attribute of the @Webservice annotation MUST be
used
> to define the name an SCA service when there is no @Service annotation
> present in the SCA component implementation or when the @Service
annotation
> is present and indicates that the Java interface or class annotated with
> the @WebService annotation defines an SCA service but the @Service
> annotation does not provide a service name.
>
> It's a mouthful. What do you think?
>
> 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:
>
>
>
> |------------>
> | From: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Bryan Aupperle/Raleigh/IBM@IBMUS
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |10/11/2010 03:42 PM
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
> |Re: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
|
>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
>
> Here is a revised proposal based on the discussion on today's call.
Since
> the test case is now positive, there is no need to update
> tuscany-oasis-sca-tests-errors.properties.
>
> [1]
>
https://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/39730/Issue%20212b.zip
>
> [2]
>
http://tools.oasis-open.org/version-control/browse/wsvn/sca-j/TestCases/?rev=201&sc=1
>
>
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> WW Center of Excellence for Enterprise Systems& Banking Center of
> Excellence Application Integration Architect
>
> Research Triangle Park, NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address:
>
>
> From: Bryan Aupperle/Raleigh/IBM@IBMUS
>
> To:
>
> Date: 09/24/2010 09:26 AM
>
> Subject: [sca-j] ISSUE 212: @Service vs. @WebService name conflicts
>
>
>
>
>
>
>
> I have uploaded a proposal for Issue 212 base on the discussion in
Monday's
> call [1]. It includes an additional normative statement in the CAA spec,
> with a corresponding Test Assertion and TestCase and comments in the CI
> spec including a reference to the CAA spec. The bulk of the test
artifacts
> for the test case are available [2]. The updated version of
> tuscany-oasis-sca-tests-errors.properties is not ready yet. Tuscany
needs
> to add a test for this mismatch and until that is done I do not know what
> the error message will be.
>
> [1]
>
https://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/39538/Issue%20212.zip
>
> [2]
>
http://tools.oasis-open.org/version-control/browse/wsvn/sca-j/TestCases/?rev=199&sc=1
>
>
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> WW Center of Excellence for Enterprise Systems& Banking Center of
> Excellence Application Integration Architect
>
> Research Triangle Park, NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address:
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
---------------------------------------------------------------------
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
