> On Mon, Nov 1, 2010 at 8:22 AM, Thomas Broyer <t.bro...@gmail.com> wrote:
>
> > Well, except that Guice for instance (and I believe JavaEE 6 too, as
> > it's based on JSR 330, lead by Bob Lee, creator of Guice) does not use
> > an XML file.
>
> Yes however I was specifically speaking to Spring DI.
>
> Isn't that somehow due to Spring insisting in "everything should be a
>
> > singleton" (and eagerly instantiating them)?
>
> I believe so, yes.
So the issue is not DI (the pattern), but the Spring framework ;-)
(and to answer my remark re. DI "that I'd encourage
*anyone* to follow", I wouldn't recommend using Spring for DI, unless
you want "configurability" through XML application contexts)
>
> My concerns aren't with MVP; from what I have read I think MVP is a very
> good design pattern & I am eager to incorporate it. My concerns are more
> aligned with the dependency on Roo & STS (which I use for Groovy and for
> Grails development & which I really like) to accomplish syncing Views &
> Presenters. I would have preferred a pure Java solution such as relying on
> the compiler and code refactoring to generate binding code where needed.
>
> Jeff
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment