Vedovato Paolo wrote: >>Unfortunately the mailing list archives aren't searchable, >>and I don't >>have the old emails anymore. If anyone can dig this up, it would be >>appreciated. >> > could be this... > http://www.geocrawler.com/archives/3/7709/2002/1/100/7451920/
Yes, this has to do with the various options of how context can be passed. With the current refactoring of ActionContext it would be possible to remove all *Aware interfaces and create ActionContextAware which would allow access to all context "in one shot". But, what would the gain be compared to using static method in ActionContext? It is definitely more code to implement interfaces and you can't do it just anywhere (you can only do it in the action class, not in classes used inside action). If we compare with J2EE, they took the route of the static method access by introducing the "java:comp/env" namespace in JNDI (which effectively is the same as a static method). It worked there, so why not here? /Rickard -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
