[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7947) 3.1 error is on class but should be on the field
Alexey Kazakov (JIRA)
jira-events at lists.jboss.org
Mon Dec 20 09:32:17 EST 2010
[ https://issues.jboss.org/browse/JBIDE-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571373#comment-12571373 ]
Alexey Kazakov commented on JBIDE-7947:
---------------------------------------
This error marker is on @Singleton annotation right now. IMO it makes sense since Singleton is a Scope. So there are two ways to solve the problem - change @Singleton to @Dependent or male the field non-public. Max, do you think we should mark the filed, not the scope annotation?
> 3.1 error is on class but should be on the field
> ------------------------------------------------
>
> Key: JBIDE-7947
> URL: https://issues.jboss.org/browse/JBIDE-7947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi (jsr-299)
> Affects Versions: 3.2.0.Beta2
> Reporter: Max Andersen
> Assignee: Alexey Kazakov
> Fix For: 3.2.0.CR1
>
>
> @Singleton
> public class Test {
> public String xxx;
> public String xyz;
> }
> Gives something like this on the class for every public field:
> Description Resource Path Location Type
> Managed bean with a public field must be @Dependent scoped [JSR-299 §3.1] MockOptionTestPlugin.java /forge-shell/src/test/java/org/jboss/seam/forge/shell/test/command line 36 CDI Problem
> That error should be on the field, not the class.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list