RE: JSP and MVC (newbie question)

Kelly,

JSP pages "auto deploy" on their own. You have no control over
authorities, ownership, compile options, etc. You can pre-compile with
some servlet containers but there are some limitations that go along
with that. Since a JSP page becomes a Servlet it is possible to do
pretty much anything a Servlet can but writing control logic in JSP is
like typing with boxing gloves on. I find it much faster to write,
debug, deploy, rewrite, repeat in real Java beans rather than something
that is generated from a script.

David Morris

>>> kc62301@xxxxxxxxx 11/5/2004 3:08:46 PM >>>
I could see maybe where debugging might be an issue,
since debugging a JSP might be different than
debugging a servlet.

But why would reuse and deployment be an issue? How
could a servlet be reused in a way that a JSP with
pure JSP tags and Java code could not? How would using
JSPs as a controll cause problems with deployment? 

Again, I just don't have a lot of experience in this
area, so I honestly don't know what kinds of issues
would arise.  

Thanks,
Kelly


--- David Morris <David.Morris@xxxxxxxxxxxxx> wrote:

> Kelly,
> 
> MVC is not enforced by any tool. Best practices and
> experience say you
> should separate your business logic from your
> control and view logic and
> that is what MVC is. Tools like JSF, Struts, Spring,
> Velocity, display
> files, Smarty templates, hibernate, EJBs, etc. just
> help you break up
> your applications into logical pieces that support
> the model, view, or
> controller. It is up to you to use them that way. I
> have never used JSP
> scriptlets or tags to build a controller and I
> wouldn't recommend it
> because reuse, debugging, and deployment will all be
> issues, but it is
> possible.
> 
> David Morris
> 
> >>> kc62301@xxxxxxxxx 11/5/2004 7:33:41 AM >>>
> I've heard of Java Server Faces but never really
> looked into them. Thanks for the lead on info on
> using
> JSF with WebSphere. I also downloaded the JSF
> reference implementation and documentation from Sun.
> 
> 
> Thanks again for the tip. I'll check it out.
> 
> Kelly
> 
> 
> --- "Bartell, Aaron L. (TC)"
> <ALBartell@xxxxxxxxxxxxxx> wrote:
> 
> > JSF (JavaServer Faces) does just that!  Aside from
> > it's custom tag
> > library (say JSP tag lib), and the tooling IBM has
> > built for drag and
> > drop UI development, it has a life cycle that it
> > goes through that
> > implements many features of MVC.  Check out this
> > tutorial to learn more
> > about JSF:
> >
>
http://www-106.ibm.com/developerworks/websphere/techjournal/0401_barcia/

> 
> > barcia.html
> > 
> > This describes the lifecycle:
> >
>
http://www.javaworld.com/javaworld/jw-11-2002/jw-1129-jsf-p2.html 
> 
> > 
> > HTH,
> > Aaron Bartell 
> > 
> > -----Original Message-----
> > From: java400-l-bounces@xxxxxxxxxxxx 
> > [mailto:java400-l-bounces@xxxxxxxxxxxx] 
> > Sent: Thursday, November 04, 2004 2:15 PM
> > To: java400-l@xxxxxxxxxxxx 
> > Subject: JSP and MVC (newbie question)
> > 
> > This is a newbie question about JSP and MVC. 
> > 
> > Since JSP is a scripting language to create
> > servlets, why not use JSP to
> > create controller servlets in MVC? 
> > A JSP does not have to contain any HTML/XHTML tags
> > at all.  It could
> > contain 100% JSP tags and Java code.
> > Using this kind of JSP for controllers would
> > eliminate the need for the
> > developer to compile code and allow greater
> > flexibility where
> > controllers are stored (servlet class files must
> be
> > in the WEB-INF
> > directory, but JSPs can be stored anywhere). 
> > 
> > However, I'm not experienced at Web development,
> and
> > there's probably
> > many things I'm not considering.
> > Please enlighten me.
> > 
> > Thanks,
> > Kelly