Spring / IoC, unit-testing (was: Which web application framework? aka Why not Struts?)

Phillip Rhodes <[email protected]>
Newsgroups gmane.org.user-groups.trijug.juglist
Message-ID <[email protected]>
---------- Forwarded message ----------
From: Phillip Rhodes <[email protected]>
Date: Dec 28, 2005 12:36 PM
Subject: Re: [Juglist] Which web application framework? aka Why not Struts?
To: Larry Karnowski <[email protected]>



On 12/27/05, Larry Karnowski <[email protected]> wrote:
>
> Phillip & Don,
> An important thing to remember about Spring is that it's really many
> projects over one common architecture.  Spring itself is just an
> "inversion of control" framework.  It's a bean container that
> instantiates and configures Java beans from an XML descriptor file.
> Plain and simple.
> <snip>
>

Yes, Spring itself will be a part of the project, that's already a given.
Actually
Spring and Hibernate are both givens.  The open issue strictly  deals only
with
the presentation layer for the web-client.  I have no experience with
Spring's
MVC framework though, which is partly why I pose this question.

> For what it's worth, I think inversion of control and Spring are the
> wave of the future, if only for the incredible ease of unit testing with
> mock objects, etc.


Oh yeah, no doubt.  IoC rules in that regard.  Although, working out how
to unit-test DAOs which encapsulate Hibernate operations is still kinda
tricky
for the same reason that all DB related unit-testing is.
Mock Object still apply I suppose, but it seems like a lot of hassle to
write
mocks to stand in for the actual database.

TTYL,

Phil

_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.