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 th=
e
> servlet stuff needs to be abstracted away and then allow for a pluggabl=
e
> 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=20
currently implementing the Portlet API (JSR168), and there's a bunch of=20
stuff there that needs to be made available to the action(if used for=20
Portlet implementation). The user is one of those things. But this=20
should only be done if the action is actually used as a portlet. So, the=20
ActionContext stuff shouldn't be bloated unnecessarily. Not sure how to=20
do this best...
/Rickard
--=20
Rickard =D6berg
Senselogic
|