Two hinderances to my own acceptance of JSP over XMLC would still be:
1. the actual *content* of those taglibs is still not 'specified visually', in such a way that a person could visualise them. [albiet, you could do two versions - a 'template' version, and a 'filled-out' version, but this doubles your maintenance woes]. This seems important to me from the perspective of communicating with the client - arguably the most difficult aspect of development for most of us.
2. [??] the file would not validate against the HTML 4.0 DTD. This seems important to me from the perspective of automating quality-assurance of HTML files.
Thanks for your tip though - JSP will at least get a look-in now, depending on it's applicability to a project!
Regards,
David.
Joe Walnes wrote:
You seem to be overlooking the most useful addition to JSP1.1 - taglibs.
With a taglib you can define you're own custom tags which can be used in
any html editor.Simple taglibs could include <bannerad />, <hitcounter />, <bigflashingbox
color="blue">Hello</bigflashingbox>.Because you can implement them yourself, the possibilities are endless and
they have greatly increased productivity in my organisation where the
developers can define custom tags and simply show the HTML people how to
use them.-Joe Walnes
Software Architect - Wirestation
-- David Bullock Project Manager - Strategic Applications [EMAIL PROTECTED]
"It's no use saying 'We are doing our best.' You have got to succeed in doing what's necessary." ...Winston Churchill LISAcorp http://www.lisa.com.au/ Adelaide Sydney -------------------- ------------------------ 38 Greenhill Rd Level 3, 228 Pitt Street Wayville S.A. 5034 Sydney NSW 2000 PH +61 8 8272 1555 PH +61 2 9283 0877 FAX +61 8 8271 1199 FAX +61 2 9283 0866 -------------------- ------------------------
