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: [OASIS Issue Tracker] Commented: (SCAJ-5) Property and reference names computed from SCA annotations in web modules not specified explicitly


    [ http://tools.oasis-open.org/issues/browse/SCAJ-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29565#action_29565 ] 

Anish Karmarkar commented on SCAJ-5:
------------------------------------

This is OSOA JIRA issue 109

opened Dec 8 2008 telecon

re-opened Aug 21 2009 telecon


> Property and reference names computed from SCA annotations in web modules not specified explicitly
> --------------------------------------------------------------------------------------------------
>
>                 Key: SCAJ-5
>                 URL: http://tools.oasis-open.org/issues/browse/SCAJ-5
>             Project: OASIS Service Component Architecture / J (SCA-J) TC
>          Issue Type: Bug
>          Components: Java EE Integration Specification 
>    Affects Versions: 1.1
>            Reporter: Anish Karmarkar
>
> Target: sca-jee-1.1-spec-wd05.doc
> Description:
> Section 6.4.3 "Providing additional component type data for web
> application" mentions that @Property and @Reference annotations can be
> used, but does not specify how the property name and reference name should
> be computed in the case where the property or reference name is not
> specified in the annotation. Note that section 6.1.4.1 gives an example in
> case of session beans. Incase of EJB's, the field name or the setter
> method name alone is good enough to compute the property or reference name
> as each EJB will result in a component. In case of a web module, since the
> entire module results in a single component, we may have to use something
> more than just the field name or setter method name as two fields with same
> name from two different web artifacts will have to result in two different
> properties or references in the computed component type. The spec has to
> make it clear how the property and reference names are computed when name
> is not specified in @Property and @Reference used on a web artifact.
> Proposal:
> In the absence of name in the @Property or @Reference annotation, prepend
> the java classname of the artifact followed by underscore to the field name
> or setter method name to compute the property name or reference name.
> For illustration, add an example with an annotated class and the computed
> component type.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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