Tell them that the taglibs are completely internationalized, whereas if they
use
scriptlets, they have to check for the ResourceBundle Locale everytime they
use a scriptlet.
So if your application is internationalized maintaining it would be a
nightmare.
Also the taglibs confirm to the latest HTML specs (or is it XHTML?),
supports CSS, does a
lot of error checking (like you can't use a Submit button if you don't use a
Form tag in your HTML).
I bet scriptlets wouldn't check for that. Errors are displayed automatically
incase of an error
.. etc... Check the documentation on Struts and i am sure that
you will comeup with a few juicy points on your own.
Hope this helps.
cheers,
Amar..
-----Original Message-----
From: D. Veniseleas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 5:18 AM
To: '[EMAIL PROTECTED]'
Subject: AW: Help me defend Struts taglibs!!!
Poor David ;-)
You can argument with the Model View Control Model and easier
maintenance....
no more idea, scriptlets are really bad....
Dimitris
> -----Urspr�ngliche Nachricht-----
> Von: Firmin David [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Donnerstag, 26. April 2001 10:47
> An: '[EMAIL PROTECTED]'
> Betreff: Help me defend Struts taglibs!!!
>
> Hi all,
> Members of my team are gradually turning against using the Struts taglibs
> and resorting to scriptlets.
> IMHO: scriptlets bad, tags good. I've had more experience in using them
> than the others, but I'm finding it difficult to fight my corner in the
face
> of ever increasing skepticism.
> Could anyone out there with really valid arguments as to why the use of
the
> Struts taglibs (especially the logic tags as they're getting the most
grief
> from my team at the moment) or taglibs in general is "good", or why the
use
> of scriptlets is "bad" help me out (in the interest of fairness, vice
versa
> arguments also happily received!)??
>
> Thanks in advance
>
> Regards
> David
>
> ************************************************************************
> The information in this email is confidential and is intended solely
> for the addressee(s).
> Access to this email by anyone else is unauthorised. If you are not
> an intended recipient, you must not read, use or disseminate the
> information contained in the email.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be
> the views of Capco.
>
> http://www.capco.com
> ***********************************************************************
