Hi Wicket folks, I've just spent some time converting a Wicket 1.2.6 / Spring 2.0 / Hibernate 3 project that we did to Wicket 1.3 beta 4 / Warp (bleeding edge ;) / Guice 1.0.
I am happy to report it went very smoothly. I actually had a question on the class hierarchy for wicket-ioc and how it relates (or doesn't) to wicket-guice. Was there a conscious design decision to not use the org.apache.wicket.injection.web.InjectorHolder class (and, by association, have the wicket-guice stuff inherit from ConfigurableInjector)? It would be pretty convenient if the GuiceComponentInjector worked similarly to the SpringComponentInjector and stuffed away a reference to the Guice injector - for easy access throughout the application, and also for easier mock testing. Just curious - thanks for all the hard work :) Peter Mularien -- View this message in context: http://www.nabble.com/Question-about-Guice-integration-with-Wicket-1.3-beta-4-tf4778901.html#a13671046 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
