After looking for sometime at using XWork as a command driven framework for desktop clients, I decided to put that to one side for the moment to instead cooperate with “Keith Donald’s”:http://jroller.com/page/kdonald work on “Spring’s”:http://www.springframework.org/ Rich Client Platform (spring-rcp). As I mentioned before I was a little frustrated by XWork’s IoC framework – the fact that you had no control over how @Interceptor@, @Action@ or @Result@ objects were created. I started looking at the problem from the point of view of integrating Spring inside XWork, and ended up with the makings of a Command Framework completely implemented using Spring. The work’s very much at a prototype phase right now, and I’ll post more information as it comes together. I’m hopeful of getting it properly integrated with Keith’s first commits for spring-rcp, and as soon as I do I’ll post some example code.
- Comment
- Reblog
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
magpiebrain 
5 Responses to “A command-driven framework for Spring”
i look forward to seeing the RCP and spring integrated.
thank you,
It would be really cool to take a look at the source, are you going to cotribute this to Spring? Will you post a link?
I’ve got a working (ish) prototype which I can post (hopefull this week – although I am very busy). The plan is for it to go into the spring-rcp project, but for this to happen I need to get it working nicely with Keith’s stuff.
I’ve just checked in this weekend the ObjectFactory stuff for XWork… Interceptors, Results, and Actions (as well as general JavaBeans used by the ww:bean tag) are now created by the ObjectFactory…
I’ve just checked in this weekend the ObjectFactory stuff for XWork… Interceptors, Results, and Actions (as well as general JavaBeans used by the ww:bean tag) are now created by the ObjectFactory…