Win a copy of Java Concurrency Live Lessons this week in the Threads forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Using just jsp or a combo of jsp/servlets  RSS feed

 
daniel schulken
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have some general questions for all jsp / servlet programmers. Has any one created a project using just jsp? If so, have you had to maintain a large project? How did that go?
I am only asking because a manager in the shop that I am working in thinks that may be the way to go for development speed.
 
Jim Petersen
Ranch Hand
Posts: 241
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I think it depends to a large on the size of the app - If its going to be small - fine just build a couple of pages with the scriplets in them. Howvever there are several warnings I should flag with this approach. If the project grows you'll find youself having to cut 'n paste more and more code and trying to fish out silly little errors caused by missing a '}' for example. 'Little' projects in my experience have a habit of growing into big projects - especially once managers see the 'magic' that you've done... Also if you leave or switch projects someone else will have to come along and figure out what you've been up to. Looking at lots of different jsps, coded on the basis of how the guy was feeling that day is not pretty and takes alot of time.
In summary do some research, map out a good architecture it will save time in the long run, based on what the goals of the project (eg time to mkt vs scalability, maintainabilty etc)
 
Steve Granton
Ranch Hand
Posts: 200
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I would agree with everything Jim says. Its really important to workout you architecture before you start and I wouldn't let the promise of speedy development influence you too much. If the architecture is wrong then you will REALLY (I can't emphasise this enough) suffer when you have to do further maintenance or add extra functionality. Remember that a fair majority of the lifecycle of a product is production and maintenance.
I've had to work on a project that used a Page Centric architecture instead of Model-View-Controller and it was a NIGHTMARE to maintain.
Before you start I would investigate the Front Controller pattern if you don't already know it. And try to use JSPs for presentation only. Leave the backend processing to a servlet, or even better helper classes.
You have been warned :-)
Cheers,
Steve
[ April 16, 2002: Message edited by: Steve Granton ]
 
Jessica Sant
Sheriff
Posts: 4313
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also -- don't forget about testing -- I just left a client site and they left ALL performance tuning and testing til the end -- when it was practically too late and too little time to do it right.
HttpUnit is a slick extension to the JUnit testing framework http://httpunit.sourceforge.net/
Might be worthwhile to check it out
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!