thanks for your reply......
even in solution 2, we could allow for some HTML code. for example, the
header and footers on a page could come from other JSPs using the include
tag. only when it comes to actual components on pages such as text boxes,
tables, etc. do we use beans which spit out HTML......do u know any sites
which have such components.....seems useful if we didnt have to write them
ourselves.......thanks for you comments though....
actually, a third idea we had (altho i dont know if it'll work) is to get
the customization properties for component from the components
themselves...hence, one could have code like this in JSPs....(where the font
color is fetched from a EJB which could have read it from a configuration
service thus making a golbal change possible with a single change to a
property....)
<tr>
<td width="27%" align="right" bgcolor="#C0C0C0"><font
color=<jsp:getProperty name = "cellFontColor"></font></td>
<td width="73%"><jsp:getProperty name="userview" property="fullUserName"
/></td>
</tr>
all comments welcome...
Rupesh.
>One thought, though -- in your solution 2 approach, there seems to be
>almost no
>value add from having JSP in the mix. Wouldn't it be easier to just write
>your apps in pure servlets in this case? (If so, there are libraries
>around that can construct DOM-style object graphs that then know how to
>render themselves as HTML)
-----Original Message-----
From: Craig R. McClanahan [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]
Sent: Tuesday, September 07, 1999 3:29 PM
To: Rupesh Choubey
Cc: [EMAIL PROTECTED]
Subject: Re: How to design a screen factory using JSP?
Rupesh Choubey wrote:
> I have a design problem, around creating screen factories using JSPs,
which
> I am trying to solve.....
>
> Goals:
>
> * Design a screen factory which is scalable (easy to produce 10
> screens or 500 screens)
> * Allow look and feel of screens to be changed globally with changes
> to as few places as possible
> (Note: we follow Model 2 in which the HTML interacts with servlets which
> interact with EJBs and then redirect to the appropriate JSP page which
have
> HTML tags and useBean tags and minimal (none?) Java code....)
>
I haven't yet had to deal with 500-screen applications (thank goodness), but
I can
sympathize with your concern. I also use the "model 2" design approach in
my
current apps, pretty much as outlined in your "Solution 1".
One thought, though -- in your solution 2 approach, there seems to be almost
no
value add from having JSP in the mix. Wouldn't it be easier to just write
your
apps in pure servlets in this case? (If so, there are libraries around that
can
construct DOM-style object graphs that then know how to render themselves as
HTML).
Craig McClanahan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
