Hi, I am not very into CDI business but here are some solutions: - upgrade Weld to 2.1.0 in Glassfish 4, if this is possible. The exception is caused by a bug in Weld 2.0.x - use Wicket 6.9.0. This will work unless you use @Inject in anonymous Wicket components. I personally never thought about this pattern before Wicket 6.9.1. I guess you don't use it too - Wicket 6.13.0 will bring wicket-cdi-1.1 module. But again it will work only if you use it with Weld 2.1.x
On Wed, Dec 4, 2013 at 5:01 PM, Diogo Casado <[email protected]> wrote: > Hello guys.. > > I'm setting up a Glassfish4 environment with wicket 6.12.0 and I > previously started using cdi to inject entity managers. > On Tomee, cdi was working but I decided that this particular > application will need a more robust JavaEE server (specially because > of OpenJPA slow pace). > > Anyway.. I'm getting warnings everywhere and specially this exception > that just broke the app: > WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] class > com....LoginPage$1 cannot be a non-static inner class > > The offending class is basically a anonymous Form.. I conclude that > any anonymous class would cause this. > > Found this ticket: https://issues.apache.org/jira/browse/WICKET-5264 > I guess it happened before and was fixed in v6.9.0 but I'm still > facing this issue with v6.12.0. > > So basically.. what's the best option: > - Apply some fix to this situation; > - Stick with a JavaEE6 with Glassfish3 while using v6.x + cdi and in > near future go for JavaEE7 Glassfish4 + Wicket v7.x & cdi 1.1 (when > ready) > - Should I forget cdi =\ > > I appreciate guidance. > > Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
