wers.
Sincerely.
PS: By the way, what does PHB stand for in ` To a PHB, every application
is a nail.'?
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Friday, February 10, 2006 3:17 PM
To: Struts Users Mailing List
Subject: Re: With a new project, what technolo
Vu, Thai wrote:
Hello everybody,
Could you give me some advices?
[...]
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 transa
, what does PHB stand for in ` To a PHB, every application
is a nail.'?
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Friday, February 10, 2006 3:17 PM
To: Struts Users Mailing List
Subject: Re: With a new project, what technologies should I use?
On 2/10/06, Vu, Th
Wow Ted, that was just about the most cliche-ridden post I've seen in a
while :) If that's what you were going for, mission accomplished! LOL
Of course, every single cliche you used is completely true and applicable
here, so no one minds I'm sure :)
--
Frank W. Zammetti
Founder and Chief Soft
On 2/10/06, Vu, Thai <[EMAIL PROTECTED]> wrote:
>. Now what should I use if I
> have to write a new web application? And correct me if I'm wrong
> anywhere please.
It's a little bit like asking a building contractor: "What materials
should I use to build a new structure?"
Just to pose a few rheto
By "knows", I mean the basics (insert/update/delete) and at least how
to do sub-selects and how to use "group by".
I do not expect *everyone* to be a stored procedure stud, but they
need to know when and how to use them if they need to, and be able to
say "I don't know, can you help me?" when need
Larry Meadors wrote:
> - iBATIS because HQL sucks, and every coder worth *paying* knows SQL
>
I'd actually disagree with this... unless we're using different
definition of "knows". Many (most?) developers might have the basics of
SQL down, but becoming an expert in SQL is the same as in any oth
"because HQL sucks" - sounds very scientific
Could you explain that please?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Meadors
Sent: Friday, February 10, 2006 11:27 AM
To: Struts Users Mailing List
Subject: Re: With a new pro
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
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:
I'd use JSF/Shale/JBoss/Hibernate/MySQL.
I've never used Spring or Shale (Although I think it'd be worthwhile after
reading about Shale) so I'll let others voice on that one.
I've only used the MyFaces implementation and didn't have any problems on
JBoss.
I've been using struts for 3 years now an
11 matches
Mail list logo
