Craig McClanahan wrote:
On 11/19/05, Laurie Harper <[EMAIL PROTECTED]> wrote:
Rahul Akolkar wrote:
Yes, that was more of a post-33064 comment.
Getting the the Struts tags to be 2.0-ready is something I'd be
interested in too. Given the origin of those tags way before 2.0,
backward compatibility issues will take precedence. I wonder if
there's a better way.
Yeah, backwards compatibility dictates that we introduce any change in
behaviour as a configurable option somehow -- possibly with a 'this will
become the default behaviour in the next release' type warning.
If you have any ideas on 'a better way' I'd love to hear them. One
possibility would be to refactor the tags so that we can produce a set
of JSP 2.0 tag files and have the tags and tag fils share a common
implementation class. Actually, that might be a better way to go than
what I've been working on in 33064!
If you guys are *really* serious about this kind of rewrite, a better
approach might just be to create a completely new alternative library with
its own URI, based on SimpleTag (JSP 2.0) instead of Tag, with a deliberate
goal of making the implementation classes extensible in the required manner.
That way, strict backwards compatibility wouldn't be required (although
you'd have to continue to maintain the old set for existing apps of course).
I'm not sure that a rewrite delivers enough benefit to justify having
two parallel implementations to maintain -- especially since these
taglibs don't get a lot of maintenance anyway...
On the other hand, lots of the things you might want to do with new tags can
already be done with JSF components, even in a Struts based app (with the
struts-faces library :-).
Yeah, I'm beginning to see that ;-)
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
