You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/06/16 17:48:22 UTC

[jira] [Assigned] (WICKET-5226) CDI integration fails in Glassfish 4.0 with WELD-000070

     [ https://issues.apache.org/jira/browse/WICKET-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov reassigned WICKET-5226:
---------------------------------------

    Assignee: Martin Grigorov
    
> CDI integration fails in Glassfish 4.0 with WELD-000070
> -------------------------------------------------------
>
>                 Key: WICKET-5226
>                 URL: https://issues.apache.org/jira/browse/WICKET-5226
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-cdi
>    Affects Versions: 6.8.0
>         Environment: Glassfish 4.0
>            Reporter: Phill Ashworth
>            Assignee: Martin Grigorov
>              Labels: cdi, glassfish, javaee7
>         Attachments: cditest.zip
>
>
> When CDI is configured in the Application and a page has a non-static inner class the page throws exception, regardless of whether there are any injected fields.
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] private  class com.inversebit.HomePage$AForm cannot be a non-static inner class
> 	at org.jboss.weld.injection.producer.BasicInjectionTarget.checkType(BasicInjectionTarget.java:81)
> 	at org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjectionTarget.java:69)
> 	at org.jboss.weld.injection.producer.BeanInjectionTarget.<init>(BeanInjectionTarget.java:52)
> 	at org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:95)
> 	at org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:78)
> 	... 65 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira