[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7710) JBT 3.2 (beta 1) saying weld archetypes are not JSR 299 compliant

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Tue Nov 23 10:24:59 EST 2010


     [ https://jira.jboss.org/browse/JBIDE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov resolved JBIDE-7710.
-----------------------------------

    Resolution: Done


So if the error marker on @Target({FIELD, METHOD, PARAMETER}) is not a bug of JBT (see WELDRAD-25) then we can resolve this issue.

> JBT 3.2 (beta 1) saying weld archetypes are not JSR 299 compliant
> -----------------------------------------------------------------
>
>                 Key: JBIDE-7710
>                 URL: https://jira.jboss.org/browse/JBIDE-7710
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299), maven
>    Affects Versions: 3.2.0.Beta1
>         Environment: Helios 3.6.1, WTP 3.2.2, m2eclipse 0.12.0, m2eclipse-wtp 0.11.1
>            Reporter: Fred Bricon
>            Assignee: Alexey Kazakov
>             Fix For: 3.2.0.CR1
>
>         Attachments: cdi-violations.jpg
>
>
> Hi
> so, using JBoss Tools 3.2.0 beta 1, I got these errors when creating a project using the weld-jsf-jee archetype :
> WidgetRepositoryProducer.java L19 : Non-static method of a session bean class has a parameter annotated @Disposes, and the method is not a business method of the session bean [JSR-299 §3.3.6]
> WidgetRepositoryProducer.java L 15 : Non-static method of a session bean class is annotated @Produces, and the method is not a business method of the session bean [JSR-299 §3.3.2]
> WidgetListProducer.java L 17: Producer method with a parameterized return type with a type variable must be @Dependent scoped [JSR-299 §3.3]
> WidgetRepository.java L 11 : Qualifier annotation type must be annotated with @Target({TYPE, METHOD, FIELD, PARAMETER}) or @Target({METHOD, FIELD}) [JSR-299 §2.3.2, §10.1]
> Dan Allen assures me the archetypes are fully compliant, so the validation implementation must be off, somehow.
> Maybe this behavior has changed in JBT 3.2 beta 2, in which case I apologize for the noise.
> Regards,
> Fred Bricon

-- 
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