Hi, The ticket and its related ticket ( https://issues.apache.org/jira/browse/WICKET-5226) explain that using CDI 1.0 in container that supports CDI 1.1 leads to these errors. wicket-cdi integration tries to process all components (even Wicket's own ones) for CDI annotations.
If you use a container that supports CDI 1.1 (like JBoss WildFly, Glassfish 4.x, etc.) then use wicket-cdi-1.1 module. Another solution is to upgrade WELD to a newer version. 2.1.2 has the fix I believe. Check Wicket mail archives for this error. There is better explanation about the problem by Emond. Martin Grigorov Wicket Training and Consulting On Tue, Apr 15, 2014 at 11:49 AM, Duke <[email protected]> wrote: > Thanks Martin, I read WICKET-5264, but I don't understand... I havn't any > injections in anonymous inner classes in my code. I try to inject > EntityManager in public class LoginPage. > If I remove any injections, fail remains. It disappers only if I remove > { new CdiConfiguration().configure(this); } in Application.init(), but my > injections are nulls in this case. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-CDI-application-junit-test-tp4665366p4665412.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
