James Cook-13 wrote: > > You could, add the bean to the servlet context, and access it via a > scriptlet in the jsp. Thus bypassing your actions all together. >
What does the Spring configuration look like for that course of action? James Cook-13 wrote: > > Or.. Create filter/Inteceptor and inject into them? > OK. We're already doing that for some of our stuff and that kind of handles our "inheritance" problem (same injection into multiple subclass types with single configuration). It feels a bit "hacky" in this context and I'd also have to make all the actions "aware" of the object being added. The other objects that we handle in this manner are genuinely integral to the Actions (data access objects and permissions filters for example). Later, Andy -- View this message in context: http://old.nabble.com/Some-Spring-Struts-questions-tp28533505p28533688.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
