The ActionContext is there to provide a ThreadLocal storage for commonly needed items... So you don't have to pass them everywhere. This would work for what you're doing, I think.
> -----Original Message----- > From: Mark Woon [mailto:[EMAIL PROTECTED] > Sent: Friday, January 16, 2004 10:31 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] ActionContexts > > > > In XWorks, what exactly is the role of the ActionContext? > Does it sort > of map to a ServletRequest in the sense that it is supposed > to hold all > the data necessary to process an Action and there will be one > for each > request? > > I'm asking because I'm trying to figure out where to store > objects that > can be used by Interceptors and Actions but don't exactly > belong in an > Action (e.g. a Connection to a database). > > Thanks, > -Mark > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, > CA. http://www.eclipsecon.org/osdn > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
