Spring-Command execution overview
I lieu of some actual code, I thought I’d post a high-ish level overview diagram of how commands are executed and handled. Those of you who’ve used XWork may notice that it looks very familiar – which is unsuprising given that I had no problems with XWorks design itself. The real benifit of this framework over XWork (in addition to the fact that it has a more fully featured IoC framework) will be that it will have a whole host of cloesly integrated UI helper classes thanks to the spring-rcp project. Due to the nature of XWork (being the underpining of WebWork) restructuring it to fit in with my goals was a non-starter.
The code is coming together nicely – adding the ValidationInterceptor is my next job, followed by the ResultInterceptor – both of which should be fairly easy.
This entry was posted on Thursday, March 4th, 2004 at 3:27 pm and is filed under Java. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.
2 Responses to “Spring-Command execution overview”
Even with the ObjectFactory? I thought that was the only sticking point? Xwork has the advantage of coming with a validation framework, type conversion, etc..
Thanks for sharing that. It’s a useful picture.
Have your say
Fields in bold are required. Email addresses are never published or distributed.
Some HTML code is allowed:
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.
Line breaks and paragraphs are automatically converted.
Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.