If the goal is to separate the life cycles or to share code, then I am
all for it.
But I don't think the end users perception is going to be any different
by this proposed change. The question is still going to be "are we
going to use a JSF or action framework?" Struts is not advocating a
preference (and I don't think it should) and I believe this is the
confusion for most people when making a choice.
/Ian
Don Brown wrote:
Ted Husted wrote:
As for making the UI tags an independant extension, a al Tiles, that
sounds good too. (Even better if we include the "value added" Ajax
support.) But I don't know if we want to hold back the SAF 2.0.0 to
make it happen. But, for phase 2, sure!
Actually, I'm thinking splitting off the tags would help us get SAF
2.0.0 out the door sooner. A lot of our remaining tickets are for
AJAX tags, which would be in this new project. As for the Tiles
comparison, that is exactly what I was going for.
And to be clear, the tags, at least for the near term, would stay
dependent on Struts Action 2. The reason to split them off would be
to give them their own release cycle and make Struts Action 2 releases
more focused and quicker. The tags have their own group of interested
committers, so I don't see a repeat of our last spinoff attempt. :)
Don
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
