You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Gilbert Kwan (JIRA)" <tu...@ws.apache.org> on 2008/04/30 22:10:55 UTC
[jira] Commented: (TUSCANY-2271) Java runtime should not inject
property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593429#action_12593429 ]
Gilbert Kwan commented on TUSCANY-2271:
---------------------------------------
Are followings right?
1. protected field and its setter is protected
- there should be no injection.
2. protected/private field but its setter is public
- field should be injected.
> Java runtime should not inject property into an unannotated non-public field
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-2271
> URL: https://issues.apache.org/jira/browse/TUSCANY-2271
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime, Java SCA Verification Tests
> Affects Versions: Java-SCA-1.2
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: Java-SCA-Next
>
> Attachments: TUSCANY-2271.patch
>
>
> Java Common Annotations and APIs v1.0 - Sec 1.8.13:
> 1349 Properties may also be injected via public setter methods even when the @Property annotation is not
> 1350 present. However, the @Property annotation must be used in order to inject a property onto a non-public
> 1351 field. In the case where there is no @Property annotation, the name of the property is the same as the
> 1352 name of the field or setter.
> Currently the properties are injected into unannotated protected fields too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.