tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harald Wellmann <>
Subject Re: TomEE + CDI + Wicket = no suitable constructor for injection
Date Fri, 04 Jan 2013 19:00:42 GMT
I don't think that's the point.

wicket-cdi [1] only depends on the CDI API, not on Weld. The Seam 
dependency is optional in fact. So it should work with OWB (but I 
haven't tried).

The message means that DetachEventEmitter is being considered as an 
injection target but does not have a default constructor.

The question is why this class is considered at all.

I suppose you have a WAR with a WEB-INF/beans.xml descriptor to enable 
CDI and wicket-cdi in WEB-INF/lib/

It might be that OpenWebBeans scans all JARs in WEB-INF/lib even if the 
individual libs don't contain a beans.xml marker (and wicket-cdi has no 
beans.xml, nor is it a CDI extension).

(I remember a discussion about Bean Deployment Archives being handled 
differently in Weld and OWB and people arguing the CDI 1.0 spec to be 
somewhat broken in this respect.)


Best regards,

Am 04.01.2013 19:33, schrieb Romain Manni-Bucau:
> wicket-cdi is for weld not for cdi if it is the one i'm thinking
> about. So this is not portable
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog:
> LinkedIn:
> Github:
> 2013/1/4 Bertrand Guay-Paquet <>:
>> Hello,
>> When running Wicket with its wicket-cdi module which provides CDI injection
>> of Wicket components, I get a ton of info/warnings of this sort:
>> org.apache.webbeans.component.creation.AnnotatedTypeBeanCreatorImpl
>> defineConstructor
>> INFO: No suitable constructor found for injection target class : [class
>> org.apache.wicket.cdi.DetachEventEmitter]. produce() method does not work!
>> I'm new to CDI so I searched online but couldn't find out what these mean...
>> Are they problematic? What do they mean? Apparently, wicket + weld doesn't
>> produce these messages.
>> Regards,
>> Bertrand

View raw message