I have now refactored ActionContext out of ActionFactory and into its own class. The AC has static methods that allow actions to access context for use in processing.
These methods duplicate the functionality of the *Aware-interfaces, e.g. "SessionAware"/"ApplicationAware". The *Aware-interfaces will most likely be deprecated in the future, and the preferred way to access context is to use ActionContext directly. This will make writing actions simpler and cleaner, and will remove the coupling of what actions do from what they look like (i.e. what interfaces they implement). /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
