i am using guice together with wicket. all component based web frameworks (wicket, tapestry, jsf, rife) need to be in charge of instantiating their objects, to manage their lifecycle. this is somewhat contradicting the idea of IoC container instantiating objects.
wicket does a good gob bridging this gap. you can use setter/field injection in web pages. it needs to use no-args constructors all over the place, not only in WebPage but also in first-order dependencies. it does tons of magic stuff re-injecting dependencies handling transient variables etc. AOP seems not possible on WebPages and components, injection of WebPages in other components is not supported and considered harmful. (sharing of components between pages in general) i think if the developers of wicket tie themselfes closer to guice - f.ex process annotations, let guice instantiate WebPage instances, integration could be much cleaner. GWT is obviously nice,i did a two week testdrive about a year ago. but my impression is i'd use it for inhouse applications, also the html/ css desingers i work with can't really take advantage of GWT, since so much is done in pure java. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
