|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--org.apache.struts.action.ActionServletWrapper
Provide a wrapper around an ActionServlet to expose only those methods needed by other objects. When used with an ActionForm, subclasses must be careful that they do not return an object with public getters and setters that could be exploited by automatic population of properties.
Field Summary | |
protected ActionServlet |
servlet
The controller servlet instance to which we are attached. |
Constructor Summary | |
ActionServletWrapper(ActionServlet servlet)
Create object and set servlet property. |
Method Summary | |
void |
log(java.lang.String message)
Log message. |
void |
log(java.lang.String message,
int level)
Deprecated. Logging should now use the commons logging |
void |
setServletFor(MultipartRequestHandler object)
Set servlet to a MultipartRequestHandler. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Field Detail |
protected transient ActionServlet servlet
Constructor Detail |
public ActionServletWrapper(ActionServlet servlet)
servlet
- ActionServlet
to wrapMethod Detail |
public void log(java.lang.String message, int level)
message
- Message to be loggedlevel
- Debugging detail level of this messagepublic void log(java.lang.String message)
message
- public void setServletFor(MultipartRequestHandler object)
object
- The MultipartRequestHandler
:FIXME: Should this be based on an "setServlet"
interface or introspection for a setServlet method?
Or, is it safer to just add the types we want as we want them?
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |