I have to agree w/ Simon on this: it really does depend on the
project, but tried and true is key - use what you know you can succeed
with. Don't experiment with real projects.
Learning new stuff is great, but getting paid is great, too. :)
I started a project in December, and went with:
- JDK5 because generics rock
- Spring because IoC makes testing painless
- iBATIS because HQL sucks, and every coder worth *paying* knows SQL
- Struts because I can find people to work on it easily
- Tomcat5.5 because i like my ${el}
For the dev side, I am using:
- JUnit
- Emma
- StrutsTestCase
- DbUnit
With this stack, you can very quickly build apps that perform like
Java should, and are 100% unit tested.
Larry
On 2/10/06, Simon Chappell <[EMAIL PROTECTED]> wrote:
> The answer is "it depends".
>
> I love playing with new stuff, but when my back's against the wall
> (corporate deadlines, gotta love 'em) I stick with the tried and
> tested. I'm leading a small project right now that we started in
> December and we're using Struts. There are a number of reasons for
> this:
>
> 1. It works.
> 2. We know it.
> 3. There are plenty of books available.
> 4. The programmers that will come after us will either know it or be
> easily able to learn it. (hence concern about book availability)
> 5. It already has corporate approval.
> 6. We can use already completed projects as sources (no pun intended)
> of example code.
>
> This is not a slam on any other framework. But, if I have not used
> them, then I'm not betting my career on them. Struts *will* get the
> job done. The other frameworks might be bigger, better, faster, more
> buzzword complient *and* make a cup of tea for me in the morning, but
> that doesn't mean that Struts doesn't work.
>
> I will learn JSF and Shale as time permits, but until then Struts
> rocks my world! :-)
>
>
>
> On 2/10/06, Vu, Thai <[EMAIL PROTECTED]> wrote:
> > Hello everybody,
> >
> > Could you give me some advices?
> >
> > Assume that I know how to use Struts, Hibernate, iBATIS and know nothing
> > about Spring, JSF (but willing to learn :) ). Now what should I use if I
> > have to write a new web application? And correct me if I'm wrong
> > anywhere please.
> >
> > I heard that Spring helps us write less code (by declaring beans with
> > their own names in xml files, whenever we need a bean, just call that
> > name) and helps us in transactions (I don't know exactly if we use
> > Spring for transaction management what we can get. Could someone write a
> > few words here?)
> >
> > I heard that JSF is best used for the view tier in the MVC model (I've
> > just read an article by Craig McClanahan named `The Best of Both Worlds:
> > Integrating JSF with Struts in Your J2EE Applications on Oracle website,
> > but it seems to me that that article applies to existing Struts
> > applications, not new ones). And if I should use JSF, which JSF
> > implementation should I use? Sun Reference Implementation or MyFaces or
> > Oracle ADF? I also heard that ADF provides the most components among
> > those 3 and it's just gone open-source (i.e. we can use it for free). Or
> > Shale (as far as I know, it is a mixture of Struts and JSF. Am I
> > right?)?
> >
> > Awaiting for your advices.
> >
> > Sincerely.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> www.simonpeter.org
> uab.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
