On Jun 14, 2006, at 11:21 AM, Joe Germuska wrote:
At 9:00 AM -0700 6/14/06, Wendy Smoak wrote:
On 6/14/06, Joe Germuska <[EMAIL PROTECTED]> wrote:
Would you consider some kind of compatibility mode? That is, before
you remove support for these, could there be a way for people to
configure things for a more strict or more compatible evaluation, to
ease migration? It seems like the closest you can get to
deprecation
warnings in tag libs/JSPs.
Rather than keep these things around in Standalone Tiles, I think the
responsibility for 'deprecation' warnings falls to Struts Action.
but in Struts action, it would only be documentation, while in
tiles, it could be done in a way that you could transition in code.
However, I realize as I write this that saddling Standalone Tiles
with that kind of weight is wrong. SAT is essentially a 2.0
release, and should clean up all these kinds of things (and I too
find the Tiles API overly cluttered, so i'm totally in favor of
these kinds of changes...)
Agreed. Part of the reason Tiles is in the shape it is in is for the
sake of compatibility. The problem is I don't think the story was
told very well. So, in a Java class you deprecate and say "use this
instead" but with Tiles the "use this instead" message was lost. The
result is you have people out there doing all kinds of things that
were "accidentally" supported. I agree that ST is basically a 2.0
version. I aim to clean it up as much as possible. I just hope we
don't lose the user base in the process.
My other comment was kind of reflexive. I suppose it could be
applied to struts-tiles -- or maybe you mean that the
responsibility falls to the struts-tiles component of struts-action?
That's the way I took it (struts-tiles). And maybe that's a
compatibility API. We wrap a struts-tiles compatibility layer around
standalone Tiles, deprecate it and add notes to the taglib doc. Cut
a release, then remove it and cut another release :-)
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
