Hello,
I think the best way is to involve XML, there are XML parsers available and
some running as servlets (http://www.alphaworks.ibm.com) and XML becoming
widely accepted standard for information interchange will proove good for
your needs (separating content from design )
JSP just like ASP, GSP etc. contain code "scriplets" that have to be
interpreted by call (request) advantage of servlets is it is pre-compiled
(runs faster, less errors etc...) so you can compare servlets to CGI but in
Java.
In any case ASP, servlets etc. you will have to merge logic and design unles
you write some extensive parsers like $field_name in .html that is filled in
with data upon request.
XML, much easier ...
ps. .jsp is invoked just like any other .html page ... web server ( such as
apache ) does routing
Dragomir Milivojevic
> Hello.
>
> 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).
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
