Patrick Lightbody wrote: > Well, for one, WebWork needs to completely remove itself from the "web". > This is WW-12 and is critical towards this goal. For example, > ActionContext.getRequest() returns an HttpSerlvetRequest object. All the > servlet stuff needs to be abstracted away and then allow for a pluggable > design that gives the developer the opportunity to dictate how > getRemoteUser() or getAttriute() or getParameter() behaves.
True. The context stuff needs to be more modular and pluggable. I'm currently implementing the Portlet API (JSR168), and there's a bunch of stuff there that needs to be made available to the action(if used for Portlet implementation). The user is one of those things. But this should only be done if the action is actually used as a portlet. So, the ActionContext stuff shouldn't be bloated unnecessarily. Not sure how to do this best... /Rickard -- Rickard Öberg Senselogic ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
