I would agree that once one is familiar with Spring, the way in which commons-chain is heavily geared towards its own XML config can be a bit challenging to ones design. I have had decent success creating chains and commands in Spring, but I use them by knowing that they are in the Spring ApplicationContext, not by asking the CatalogFactory for them. There's a decent amount of low-level plumbing in both commons-chain and Struts 1 that are overly committed to the first way we thought of hooking all that stuff together.
On 2/22/07, Paul Benedict <[EMAIL PROTECTED]> wrote: Now that I slept on it.... :-) Based on the advice, It sounds like I should write a Struts Plugin to expose any kind of variable into application scope. Then pull those out inside of execute(). On this front, Spring has a few classes that can help move things between the Spring Application Context and the Application Context * ServletContextAttributeExporter "takes Spring-defined objects and exposes them as ServletContext attributes" * ServletContextAttributeFactoryBean "fetches a specific, existing ServletContext attribute [and e]xposes that ServletContext attribute when used as bean reference, effectively making it available as named Spring bean instance." May save you some coding...Joe -- Joe Germuska [EMAIL PROTECTED] * http://blog.germuska.com "The truth is that we learned from João forever to be out of tune." -- Caetano Veloso
