On Sat, Jan 22, 2011 at 6:02 PM, EECOLOR <[email protected]> wrote: > It's a simple url --> controller method use case.
I've just done something similar. On my first attempt, a while back, I tried it your way. This time I simplified it a lot by restricting Guice-injected objects to the constructor. Otherwise, you have to figure out what is coming from Guice and what is coming from the HTTP request. Mapping request parameters to objects is enough work as it is. BTW, if anyone knows of a standalone library that does that, I'd be very interested. Moandji -- 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.
