struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manomohan K Kalathil" <>
Subject RE: Struts Productivity Survey
Date Sat, 11 Jan 2003 06:17:15 GMT
Agree completely with what Jaaron has to say. Your best bet is to divide up
the work. There could be people who are good at JSPs, taglibraries, HTML. Few
others who have exposure to web development using servlets etc should be
trained indepth on struts and be asked to develop all actions and associated
artefacts. Note however that this approach requires that the lead of the team
should have his/her fingers into all pieces of the pie. In your case you will
need more than one lead and the leads should know and enforce the interfaces
between the web team and the struts team and the business layer folks. I have
been on one such role and believe me it is quite nightmarish for the first
few weeks. But once everyone gets a hang after the first integration. 

-----Original Message-----
From: J Aaron Farr []
Sent: Saturday, January 11, 2003 4:55 AM
Subject: Re: Struts Productivity Survey


I had a similar situation recently, although not nearly at the scope you're
currently facing.  I'm not sure if it was an advantage, but I had a handful
developers who were completely new to java, object-oriented programming,
everything.  One had some COBOL experience, the rest were database people
(Oracle P/SQL programmers).  Luckily I had the other project leader on my
and he agreed Struts was the way to go.

Personally I think Struts is easy to grasp IF you break it down.  My plan was
something like this:

1. Get everyone up to speed on the general idea of MVC and Struts.  Basic
definitions.  Perhaps show an extremely trivial example.

2. Divide up the work.  View people don't need to understand how Actions work
completely.  Likewise Action and Model people don't need to understand Views
Taglibs.  As long as you have well defined interfaces and know what needs
passed to what, you can teach people on a need-to-know basis.  For many
developers I think this is easier.  It gives them something to work on.  The
ambitious ones will do their own homework.

3. Develop one part of the application completely to be used as a reference. 
In my case, the application had three main parts to it.  I wrote almost all
part one, and then turned it over to the team for parts two and three.  I did
complete walk through with them and then after that I was just on support.

We had the whole process moving within a week.  It was a hectic week mind
but it worked and things got done the right way.  I think Struts easily lends
itself to group development and if you have a couple of knowledgeable people
charge, the rest can do good work without really understanding everything
the framework.

Good Luck!

Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message