Joe Germuska wrote:
So, I really do have work I should be doing, but I couldn't help looking
around XWork a little bit, and I'm just wondering why Ti needs to use
both it and Spring anyway?
What are the various services offered by each that aren't offered by the
other?
I should really list this out on the wiki site. The short of it is XWork gives us an Action framework, interceptor
chains, expression language support, l18n, validation, and the value stack. WebWork gives us all their result types and
neat tag libraries that can be used with any template technology.
I like working with XWork and WebWork2 because it is similar enough to Struts classic that we can provide near
backwards-compatibility, yet it is written very well, and brings a bunch of new features we can get for free.
Furthermore, I think there is a lot of synergy to be had between the two teams for each to explore new features that can
be easily shared back and forth.
Don
Joe
At 2:44 PM -0500 8/31/05, Joe Germuska wrote:
I don't know anything about how XWork will handle message resources,
but what I'm talking about is all internal to Struts anyway, so I'm
not sure that the user needs to be concerned; this is more about an
alternative to all the LocalStrings.properties files which Struts
classes currently have to bootstrap themselves.
Until I see it, I won't argue very hard for using Spring as the
message resolver, but I am finding it handy inside my own
applications. Are there any places in Struts Ti where XWork's message
facilities are being used?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
