Hi Diogo, It already is: https://github.com/apache/wicket/blob/wicket-6.x/wicket-experimental/wicket-cdi-1.1/pom.xml#L45
There are no dependencies on weld packages, as wicket-cdi-1.1 is fully portable. It only has a testing dependency on cdi-unit, which depends on weld. Emond On Tuesday 10 December 2013 09:07:52 Diogo Casado wrote: > Edmond, > > Please when you assembly the package for the new CDI version, use > scope provided for javax.* and org.jboss.* dependencies. > I'm fixing the plumbing of my project and several undesired packages > are being assembled because of current wicket-cdi. > Thank you for your efforts! > > - Diogo > > On Thu, Dec 5, 2013 at 6:09 PM, Emond Papegaaij > > <emond.papega...@gmail.com> wrote: > > The new module should be fully functional, including all scopes. The > > performance should be much better than with the old module, due to > > InjectionTarget caching. The biggest changes are in conversation > > propagation. If you do not use the conversation scope, the transition to > > the new module should be very smooth. > > > > Best regards, > > Emond > > > > Op 5 dec. 2013 20:24 schreef "Diogo Casado" <diogocas...@gmail.com>: > >> Thanks Emond, > >> > >> I will watch the progress and report back. > >> For now.. I'm ignoring the warnings and using a snapshot from glassfish. > >> I'm using CDI just for EntityManager injection..and it's just > >> RequestScoped. > >> So.. from what I saw in the current version, the biggest problem would > >> be if it was context oriented. > >> > >> Regards, > >> Diogo C. > >> > >> > >> On Wed, Dec 4, 2013 at 7:01 PM, Emond Papegaaij > >> > >> <emond.papega...@gmail.com> wrote: > >> > Hi Diogo, > >> > > >> > Please note that wicket-cdi-1.1 is still experimental. I do have high > >> > confidence it will work fine, but it has not been tested extensively. > >> > The > >> > API is mostly compatible with the current wicket-cdi module. One of the > >> > changes is that the constructor of the CdiConfiguration no longer takes > >> > a > >> > BeanManager. CDI 1.1 has several portable ways of looking up this > >> > BeanManager. A fallback is added (see CdiConfiguration), in case your > >> > environment does not provide any of the portable lookup methods, but > >> > Glassfish should. Also, it is no longer possible to disable injection > >> > of > >> > various Wicket classes. Components, behaviors, sessions and the > >> > >> application > >> > >> > are always injected. > >> > > >> > A major difference in behavior is the way conversations are propagated. > >> > >> The > >> > >> > current cdi module uses non-portable code (which only works with Weld) > >> > to > >> > propagate the conversation. wicket-cdi-1.1 always propagates the > >> > conversation via the url (with the cid query-parameter), which is > >> > >> portable > >> > >> > across all CDI 1.1 providers. > >> > > >> > As Martin mentioned, wicket-cdi-1.1 requires a recent version of Weld > >> > (if > >> > used with Weld). Weld 2.1.1 (which has not yet been released) has some > >> > fixes regarding warning floods ( > >> > >> https://issues.jboss.org/browse/WELD-1547). > >> > >> > Until then, you either have to ignore the warnings or lower the logging > >> > level. > >> > > >> > To use wicket-cdi-1.1, once wicket 6.13 is released, add the following > >> > dependency: > >> > <dependency> > >> > > >> > <groupId>org.apache.wicket</groupId> > >> > <artifactId>wicket-cdi-1.1</artifactId> > >> > <version>0.2</version> > >> > > >> > </dependency> > >> > > >> > Until then, you can test with 0.2-SNAPSHOT. You can find the details > >> > for > >> > the snapshot repository on our download page. > >> > > >> > If you find any issues with wicket-cdi-1.1, please file JIRA issues and > >> > assign them to me. > >> > > >> > Best regards, > >> > Emond Papegaaij > >> > > >> > > >> > On Wed, Dec 4, 2013 at 7:02 PM, Diogo Casado <diogocas...@gmail.com> > >> > >> wrote:
