To my mind, jsp just doesn't solve my problems at the right level. This is especially true where interfaces to databases are concerned. We've been using xsql (which is an oracle product) for a couple of years now, and in most cases we can get a good degree of separation between the database/bussiness logic from the presentation stuff (which we do in xsl). Customer requests like "please put totals on that table, and sort it on this column" can be done easily without involving (or understanding java or having permission to change the sql). This separation also applies on the input side too. I understand that with the right tag libraries and beans we could get a similar effect, or use jsp to create xml and then transform that with xsl. I think I'm right in saying that most of the above applies to cocoon. Tim.
URL: http://www.westpoint.ltd.uk/ - internet recon. ___________________________________________________________________________ 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
