Padhu,
I can suggest our product TICL (however, it's only free for
non-commercial use). Get it http://www.kobrix.com. It is component
based, so you put UI components in your JSP and respond to events. Every
JSP page that you write in TICL has in a way its own controller
encapsulated in a top-level tag and you can compose more complex
pages by including smaller ones without worrying much which does
rendering, which creates beans etc. Look&feel in TICL is not specified
in the JSPs at all. Every component has a high-level style used to
render it. So you will define a consistent, common look&feel for all
your pages in one place: a TICL style sheet. For example, the JSPs in
our have almost no pure HTML (except in a few places where tables are
used for layout).
Best,
Boris
Borislav Iordanov
Chief Architect
TICL - a RAD toolkit for server-side Java
http://www.kobrix.com
> -Original Message-
> From: A mailing list about Java Server Pages specification and
reference
> [mailto:JSP-INTEREST@;JAVA.SUN.COM] On Behalf Of Padhu Vinirs
> Sent: Sunday, October 27, 2002 7:48 PM
> To: [EMAIL PROTECTED]
> Subject: web application design question...
>
> I am planning on designing a web app. This web app basically has one
> look and feel ( like an amazon.com ) but where the contents change (
> including images, amount of text/links etc ) depending on user
choices.
> I am aware of Struts framework and the Front controller design
pattern.
> I think Struts might be overkill because of the same look and feel
> across the webapp.
>
> My question is: Should the look and feel be :
>
> 1. managed by one jsp page which calls different controller objects (
> which print portions of the UI )
> 2. one jsp page which calls different controller objects which update
> javabeans, which in turn the main jsp page renders. So all rendering
is
> done by only one jsp page, which acts as the front controller also.
> 3. one jsp page, which includes different jsp pages depending on the
> requirements. The smaller jsp pages inturn call controller objects,
read
> from model/javabeans etc to render the UI. The main jsp page acts as
the
> front controller.
>
> I prefer (3), but making sure the different JSP pages maintain the
same
> look-and-feel standard is going to be tricky.
>
>
> I would like to hear comments from anybody who has designed similar
> projects. Also any good book recommendations is appreciated.
>
>
> Thanks
>
>
> -- padhu
>
>
==
> =
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-
> INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
> DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://archives.java.sun.com/jsp-interest.html
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.jsp
> http://www.jguru.com/faq/index.jsp
> http://www.jspinsider.com
===
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://archives.java.sun.com/jsp-interest.html
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.jsp
http://www.jguru.com/faq/index.jsp
http://www.jspinsider.com
