Noel J. Bergman wrote:
Don Brown wrote:
Sean Gilligan wrote:
Don Brown wrote:
That said, if Roller is considering upgrading to Struts
Action 2, I'd be more than happy to help out, as it
would help us focus our migration tools simultaneously.
I'm prepared to sign up to finish the port of the Blog UI
component to SpringMVC, but don't think I'll have the time
to learn WW2 and do the work.
Honestly, I don't really see the value. For this simple use,
there isn't anything one can do the other can't. I'd say the
best bet is to try to make your class a POJO which could
definitely work in WW, and probably Spring.
To be clear, are you saying that Sean could do less work -- and work that he
would be doing anyway -- and that you are offering to help do the neccessary
work to do the SAF2 bits, educating the Roller team in the process?
Sure, I'll help in any way I can. However, I wouldn't move to Struts Action 2
today (unless you want to be really cutting edge) :), so that leaves WebWork 2
and Spring. Moving to WebWork will get you 90% of the way to Struts Action 2,
however, if you'd rather just go with something that is more familiar, I'd
completely understand.
I don't know Spring MVC, but Spring as a project is pretty good about staying
out of your code, as is WebWork, so whatever you choose, it should be pretty
trivial to switch from one to another.
At the end of the day, those willing to do the work make the decisions, so let
me know how/if I can help.
Don
--- Noel
