A while back we did a 'pure' servlet
project (no jsp, no xml) writing
direct to an oracle db.
We validated on the client side
(size, type, not null) using
the table's meta-data to generate
the html. We then inforced the
bussiness rules (they were simple)
in triggers (via jdbc) in the servlet.
We had
a layer that translated oracle
error numbers (in thrown exceptions) into suitable error messages, by looking at which
fields in could throw that exception
(again from the meta-data)
I'm not sure I'd do it exactly the
same way again, but it works
ok if the bussiness logic is simple.
In that case there was a pretty
simple mapping between html pages
and database tables and views.
This time around I'd probably use
xsl to convert the error numbers
to relevant text.
Tim.
http://www.westpoint.ltd.uk/
Internet reconnaissance services.
___________________________________________________________________________
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
