• Post Reply Bookmark Topic Watch Topic
  • New Topic

real project ... real problem (JSP or Servlet)

 
Josue Cedeno
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am currently working on a project which passes form data to retrieve data using a stored procedure. It is a basic commission report.
The current IT team uses servlets heavily, but I wonder if JSP would offer a more efficient solution.
Is an MVC solution using JSP(view), Servlets(Controller), Bean(Model) the optimal solution for this project?
(This is a sincere question, but also a ploy for a free servlet reference book)
 
Frog Killer
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How are u look on the EJB?
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"FrogKiller",
The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp .
We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please edit your profile and select a new name which meets the requirements.
Thanks.
Dave
[ May 21, 2002: Message edited by: David O'Meara ]
 
Corey McGlone
Ranch Hand
Posts: 3271
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It really depends upon the details of the project. You've only given a brief description.
In general, going to a MVC architecture, you'll increase the complexity of an application but, if the application is of any respectable size, the gain you'll receive from the separation of tasks will be well worth it.
For example, let's say that you use servlets and supporting classes to perform your business logic and your JSPs to display data. Some time down the road, if you'd like to change the way data is displayed, you need only to update the JSPs. In addition, if the JSPs are written well (with little Java embedded in them), they could be updated by someone that doesn't know Java.
However, if you continue to use only servlets, any changes will require a Java expert to dig into the servlets and make the changes.
I've only brushed the surface of the various strengths and weaknesses of the MVC architecture. You could get yourself into an awfully long conversation about it around here.
Actually, there was a recent thread that discussed some of these topics somewhat.
I hope that helps,
Corey
 
Rishi Singh
Ranch Hand
Posts: 321
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Cedeno,
whether to go for JSP(View),Servlets(Controller)and Bean(Model) or a full Servelet Architecture or an EJB centric architecture depends entirely on the complexity, extent, nature and the user base of the project.It has to be decided during the analysis phase.But for a medium size project a full servlet based architecture may suffice.
Rishi Singh
SCJP,SCWCD
 
Malhar Barai
Author
Ranch Hand
Posts: 399
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
dear josue
using MVC depends mainly on the size of your project. if its mid sized & complexity of the project is less, go along with servlets, no problem.
but if lot of business logic is involved, go in for EJB stuff.
HTH
malhar
 
Axel Janssen
Ranch Hand
Posts: 2166
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would propose apache.struts as solution.
You could argument that you and your co-workers could learn s.th. which to use in other projects.
Reusability might still be a buzz-word for your boss.
I wouldn't try ejb. It has a steep learning curve for middle-clever people like me (am doing that).
Axel
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!