Ted Stockwell wrote:
> I think that either straight servlets or JSP would be a good choice.
>
> Currently, I am generating HTML documentation from JSPs. There are many
> names and such whose values come from a bean. I edit and recompile the bean
> to change values in the documentation.
> I also have beans that generate HTML objects like tables and stuff. I add
> values to the bean and then ask the bean to give me the HTML for the entire
> table. A OO HTML framework might be a better way to go here, this way works
> for me right now.
> I also have a bean that isolates the layout of my pages from the content.
> It has a property named "Content", I generate the content that goes into a
> page, set the content property of the bean, and then get the HTML for the
> entire page from the bean. This way I can change the LAYOUT of all my pages
> by changing a single bean (if not using frames then put a toolbar at the top
> or put the toolbar on the left, if using frames then do nothing, change
> margins, background color, etc, etc.). There are lots of games you can play
> this way.
>
> I think that you should make the choice between servlets and JSP based on
> who will be creating the pages. If geeks(sorry, I mean, developers) are
> going to make the pages then using straight servlets and an OO framework
> that generate's HTML (like Weblogic's htmlKona framework) might be the best
> choice. If designers (non-geeks) are going to make the pages then JSP would
> definitely be the better choice, designers create HTML and use JSP tags to
> connect to beans (easier said than done but theoretically everything's
> great...).
Theoretically Yes. In practice though not the same. Case in point I created
some jsp files and gave it to a designer to enhance. It was rather confusing to
him. Forget about those simple examples demonstrated in the specs. If you
create a a more complex jsp page with jsp tags in textfields, url links etc. the
jsp page when viewed by a browser looks messy and confusing. Most web
development tools use a
browser to preview pages. So until browsers are made to ignore jsp tags you
will have a very hard time convincing a designer that jsp is the best thing
since slice bread. Which means the java developer is also the web designer too.
>
> Definitely make a small prototype before you commit to anything.
>
> ted stockwell
>
> > -----Original Message-----
> > From: Timothy Gallagher [SMTP:[EMAIL PROTECTED]]
> >
> > I have an interesting problem and I'm not sure if it is appropriate as
> > servlet or through some other technique.
> >
> > I need to create a site that, once finished, will allow me to copy the
> > site to another server and allow the new server to change some of the
> > characteristics. A simple example would be to allow the title to
> > change to reflect the new server. There will be about 30 pages total,
> > so hand editing will become overwhelming, although once the majority of
> > the editing is done, it will not be done again.
> >
> > Is this best with JSP, servlets, or some other method?
> >
> >
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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
