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!
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
