Lance,
Keep in mind the terms "Model I" and "Model II" are not really being thrown
around anymore given the 1.0 spec adoption of a variety of different models.
These are more architectural models than design patterns.
Cheers,
Dan
--
Daniel Kirkdorffer
NACN IS: 425-580-6225
Sr. Consultant, Syllogistics LLC
Email: [EMAIL PROTECTED]
Web: http://www.syllogistics.com/
> ----------
> From: Lance Lavandowska[SMTP:[EMAIL PROTECTED]]
> Reply To: Lance Lavandowska
> Sent: Monday, June 21, 1999 5:49 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Servlet->JSP question
>
> While it won't provide an answer, you may gain some insight by reading
> http://www.aptura.com/technology/jspBook_Architectures.html . I'll warn
> you, I haven't finished writing it yet. It is part of an effort by
> several people to write a "book" on JSP.
>
> If you're interested in more, check out
> http://www.esperanto.org.nz/jspbook
>
>
> Lance Lavandowska
>
> -----Original Message-----
> From: Alik <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Sunday, June 20, 1999 9:51 PM
> Subject: Servlet->JSP question
>
>
> >Hello.
> >
> >First of all, I am new to this list, so if the question I am asking was
> >previously covered, please point me to the appropriate archive (and
> accept
> >my appologies)
> >
> >I am trying to build an application that separates business logic from
> >presentation (i.e. I want to allow my designers to work separately from
> >programmers).
> >Most "large" systems that do that (like Locomotive), although do a good
> job,
> >require their proprietary engines - i.e. they are not fully servlet
> comliant
> >and can't run under a generic Servlet runner.
> >Couple systems that I looked at - WebMacro most notably - provide
> excellent
> >functionality, but, again, are not standards based (i.e. they have a
> >proprietary markup language).
> >So now I am settling on Servlet/JSP combination, where the servlet
> performs
> >all processing, then constructs a bean with data, selects a JSP pages and
> >uses it to render the data. (This can easily be changed to XML, for
> example,
> >by using XML/XSL parsers to process the bean, instead of the JSP engine).
> >
> >My two questions are:
> >1) Does this look like a sound architecture choice? (Any other
> suggestions?)
> >2) How do I invoke JSP from a servlet? In JSDK2.1 there is
> >'RequestDispatcher.forward()', but that seems to allow the browser to
> access
> >that JSP page directly (i.e. if I can call 'forward("/foo.jsp")', the
> browser
> >can call 'http://myhost.com/foo.jsp' [ignoring the incorrect semantics of
> >'forward' I used] ) - which is really bad (and I do not want to get into
> the
> >game of setting the web-server to disallow access to certain pages from a
> >browser).
> >
> >Thanx in advance for your help.
> >
> >--------------------------------------------------------------------
> >
> > _/_/_/_/ _/ _/ _/ _/ http://Orbit.Stanford.EDU/~alik
> > _/ _/ _/ _/ _/ _/
> > _/_/_/_/ _/ _/ _/_/ ftp://Orbit.Stanford.EDU/people/alik/
> > _/ _/ _/ _/ _/ _/
> >_/ _/ _/_/_/_/ _/ _/ _/ mailto:[EMAIL PROTECTED]
> >
> >--------------------------------------------------------------------
> >
> >=========================================================================
> ==
> >To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> >of the message "signoff JSP-INTEREST". For general help, send email to
> >[EMAIL PROTECTED] and include in the body of the message "help".
> >
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
