We are currently using Webwork2 - XWork with PicoContainer. I must say that this combination really rocks. For those who are using other IOC containers (Spring and Avalon), have a look at Pico it is amazingly simple but makes your code sooo clean.
The integration is well laid out (Great stuff by Joe Walnes). Still a few issues that we are currently working on but workable. Anyway, I should get to the real point of my post which is : We are looking at making interceptors pico component themselves which would allow to use pico's magic to get other components to be used from interceptors. I am not familiar with XWork's code base. A quick look makes me think the interceptors are instantiated once for a given action type. Am I right? Where this is done? If interceptors are instantiated once, this would limit us to the components that are registered in the application scope pico container but still would be very interesting. Cheers, François ___________________________ François Beauregard, b.ing. Vice-président Recherche et développement Pyxis Technologies www.pyxis-tech.com T : (450) 681-9094, poste 102 F : (450) 681-5758 [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
