Gregg Bolinger-7 wrote: > > Looks much better Sam. :) I'm curious as to why you needed a custom > action resolver. Was it to get Guice available in the ActionBeanContext? >
Thanks Gregg. The custom ActionResolver is to allow constructor injection. It lets Guice create the ActionBean instance rather than using Stripes' Class.newInstance() in makeActionBean(). If the GuiceActionResolver is not specified, all the other injections work, just not constructor injection on the ActionBean. I really wish there was a cleaner way to create the ActionBean, I generally dislike inheritance and it seems heavy handed to force my ActionResolver on someone. I really like constructor injection though, as it makes it trivial to identify dependencies at test-time. Sam -- View this message in context: http://www.nabble.com/Ann%3A-Stripes-guicer-%28Guice-for-Stripes%29-tp17649051p17675307.html Sent from the stripes-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
