Comments on: XWork for Swing? http://www.magpiebrain.com/blog/2004/02/18/xwork-for-swing/ Sam Newman's blog Sat, 05 Jul 2008 00:38:13 +0000 http://wordpress.org/?v=2.5.1 By: Sam Newman http://www.magpiebrain.com/blog/2004/02/18/xwork-for-swing/#comment-188 Sam Newman Thu, 19 Feb 2004 00:33:42 +0000 http://www.magpiebrain.com/2004/02/18/xwork-for-swing/#comment-188 The integration examples for both Spring and Pico cover integration with WebWork 1.4, but not 2 or with XWork itself. I think I'll run before I can walk - get Swing using WorkX (assuming I can get it built - the build seems a little groked right now) as a command framework interfacing with a Spring powered IoC Layer. Then I'll look at interating Spring into XWork proper. I would hazard a guess that XWork's existing IoC capabilities (it is after all a form of IoC frameowkr itself) could be completely replaced behind the scenes with either Pico or Spring. I guess Pico would be the favorite given the size, but Spring is more mature, has better support and better docs... The integration examples for both Spring and Pico cover integration with WebWork 1.4, but not 2 or with XWork itself. I think I’ll run before I can walk – get Swing using WorkX (assuming I can get it built – the build seems a little groked right now) as a command framework interfacing with a Spring powered IoC Layer. Then I’ll look at interating Spring into XWork proper. I would hazard a guess that XWork’s existing IoC capabilities (it is after all a form of IoC frameowkr itself) could be completely replaced behind the scenes with either Pico or Spring. I guess Pico would be the favorite given the size, but Spring is more mature, has better support and better docs…

]]> By: jez http://www.magpiebrain.com/blog/2004/02/18/xwork-for-swing/#comment-187 jez Wed, 18 Feb 2004 20:36:00 +0000 http://www.magpiebrain.com/2004/02/18/xwork-for-swing/#comment-187 As it says here ( http://wiki.opensymphony.com/space/Struts vs. WebWork ) you only have to implement the Action interface, so your actions are nearly, but not quite unaware of their container. The PicoContainer usage has already been done ( http://wiki.opensymphony.com/space/PicoContainer Integration ), try to use this instead of the FooBarAware IoC stuff they started with. Be interested to see how you get on with Swingifying it all... jez. As it says here ( http://wiki.opensymphony.com/space/Struts vs. WebWork ) you
only have to implement the Action interface, so your actions are nearly,
but not quite unaware of their container.

The PicoContainer usage has already been done ( http://wiki.opensymphony.com/space/PicoContainer Integration ), try
to use this instead of the FooBarAware IoC stuff they started with.

Be interested to see how you get on with Swingifying it all…

jez.

]]>