The only thing "external" is the conversation management stuff from Seam, it looks like. The user would have to make sure they include the container-specific "adapter" code on the classpath (org.jboss.seam.conversation:seam-conversation-weld for example) for their CDI container.
Another concern would be the fact that they (JBoss) don't "publish" their artifacts to Maven central. Aren't they (the managers of Maven central) frowning upon publishing artifacts up there that depend on artifacts published elsewhere? On Wed, Nov 16, 2011 at 4:21 AM, Martin Grigorov <[email protected]> wrote: > one more question: is there anything Weld specific in wicket-cdi or it > should work with other CDI implementations too ? > > On Wed, Nov 16, 2011 at 11:20 AM, Martin Grigorov <[email protected]> > wrote: >> speaking of moving it to Apache.. >> >> currently we have some inconsistencies between Spring and Guice >> integrations and users ask from time to time : >> - why we don't use jsr330 @javax.inject.Inject since both Spring and >> Guice support it. With CDI I think javax.enterprise.inject.Inject is >> used which is yet another ... >> - is it possible to not proxy the injected object (we have a ticket >> with patch for Spring for that but not for Guice) >> >> now with CDI I see more: >> - why Injector.get().inject(me) doesn't work ? >> --- because it needs BeanManager, but since it is reachable from >> ServletContext then it should be OK >> --- because it needs the class - OK, use me.getClass() for that >> - why Spring/Guice doesn't support @PostConstruct ? >> >> So my question is: should we try to make them consistent with each >> other or we should provide minimal integration and give the user the >> possibility to use the full power of his favorite DI framework ? >> >> On Wed, Nov 16, 2011 at 10:52 AM, Igor Vaynberg <[email protected]> >> wrote: >>> sure >>> >>> -igor >>> >>> On Wed, Nov 16, 2011 at 12:49 AM, Martijn Dashorst < >>> [email protected]> wrote: >>> >>>> On Tue, Nov 15, 2011 at 7:00 PM, Igor Vaynberg <[email protected]> >>>> wrote: >>>> > if you want to learn how to use CDI with Wicket i just wrote a short blog >>>> > about it: >>>> > >>>> > https://www.42lines.net/2011/11/15/integrating-cdi-into-wicket/ >>>> >>>> Can we use it for the documentation of the CDI project (when we >>>> migrate it to apache)? >>>> >>>> Martijn >>>> >>>> -- >>>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
