...
xaction output | Java type | expected Action bean method (Java) |
---|---|---|
<myOutput> (no type specified) | user specified | public SomeType getMyOutput() { ... |
<myOutput type="content"/> | java.io.OutputStream | public void setMyOutputStream(OutputStream o) |
Resources
Resources are treated much like inputs in that they are processed prior to executing the Action bean. As illustrated below, when the Action framework finds a resource specified in the action-resources section of your action definition, it will get a handle to that resource in the form of an InputStream and hand that object to your Action bean.
xaction resource | Java type | expected Action bean method (Java) |
---|---|---|
<myResource type="resource"/> | java.io.InputStream | setMyResource(InputStream o) { ... |
|
|
Resources
...
Action Error Handling
FAQ
How are Actions different than POJO Components? I thought POJO Components already supported the ability to drop in a Java bean and have it work as a "component".