---------------------- Forwarded by Glen C. Hawkins/Users/Skyway on
10/27/99 09:27 AM ---------------------------


[EMAIL PROTECTED] on 10/26/99 05:41:13 PM

To:   [EMAIL PROTECTED]
cc:    (bcc: Glen C. Hawkins/Users/Skyway)
Subject:  RE: Enhydra XMLC vs. JSP




G'day Glen,

I have used both JSP and Enhydra XMLC.  I found JSP really quite effective
in separating presentation and business logic (but it is a little too
easy inadvertantly putting too much business logic in the JSP).

Things that I found with XMLC (which is just my opinions)
- The fact that you need to manually compile your templates every time
  you change it is annoying.  This requires a little knowledge, I believe
  of java packages, where to put your class file etc.  It would be miles
  better if it were generated on the fly.
- It's good that you can use other Web Dev tools like Dreamweaver and
  Hot Dog.  (But no FrontPage - it really alters your HTML without telling
you
  a little too frequently - this really can mess up the layout of your
  XMLC template).
- I sort of remember that the setter methods to set the values in variables
  in the template always change names depending on the name of the template
  variable.  This was a bit annoying.
  A better strategy would have been to just have one method which could
  change all template variables just by supplying the name of the variable
  you want to set.
- Found that tables and lists (bulleted and numbered) were a little
difficult
  to do.


Things that I found with JSP
- I just love the power of the scriptlets etc.  Although with power,
  there is also misuse of power.  And it is easy to put too much logic
  inside your JSP.
- I love the autocompilation feature and the errorPage directive.



With both:
- It is still a little bit difficult (in Australia and possibly the US as
well), to get web page designers to use any of these two technologies.
They are more familiar with ASPs.
- They are great to separate logic and presentation.

I personally like JSPs as it allows me to separate presentation better.
Using XMLC, it requires most of the presentation in the Templates, but
still
some of the presentation inside the servlet as well (replace this
template variable with this value etc).  That is my personal opinion.

Remember, this really is just my personal opinion and I am sure there
are many other people who swear by XMLC.

Hope that helps,


Ho

===========================================================================
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

Reply via email to