ISSUE-111: @Constructor value attribute should not be optional

http://www.osoa.org/jira/browse/JAVA-111

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:

Simon Nash ---12/05/2008 11:29:45 AM---TARGET: Java Common Annotations and APIs DESCRIPTION: @Constructor value attribute should not be opt

From:

Simon Nash <>

To:



Date:

12/05/2008 11:29 AM

Subject:

[sca-j] NEW ISSUE: @Constructor value attribute should not be optional

TARGET: Java Common Annotations and APIs

DESCRIPTION: @Constructor value attribute should not be optional

The current description of the @Constructor attrbute says that the

value attribute is optional.  However, without this attribute, there

is no reliable way of determining the property or reference names.

The Java constructor parameter names cannot be used, because these

are not normally available via Java introspection.

PROPOSAL:

The following line numbers refer to the JavaCAA CD01 document.

1. Replace lines 1014 to 1016 by

    public @Interface Constructor {

        String[] value();

    }

2. In line 1021, replace "value(optional)" by "value".

3. On line 1023, add a new sentence "The length of the array MUST be

    the same as the number of constructor parameters."

4. Replace line 1032 by

    @Constructor("someProperty")

---------------------------------------------------------------------

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