...
The Action framework expects Action objects to be Java bean compliant with respect to setting inputs, setting resources, and getting outputs. In other words, if your action needs takes a string input, the action definition in the xaction solution file will specify this string input, and the Action framework will cause that value to be set via a setter method on the Action object. You do not see parameter Maps and such in the Action API for this reason. All inputs, output, and resources IO will involve Java bean reflection on your Action object to find the appropriate IO methods.
See the Echo Plugin - a sample plugin for the BI PlatformBIServer project for examples of how to get data into your IAction and how to expose the output of your IAction so something else can do something with it (i.e. display the results of your IAction, pipe them to another step in an action sequence, or bind them to a session parameter).
...
| Code Block |
|---|
public class MyAction implements IAction {
public void setAttachments(int index, Object o)
{ //do something }
public Object getAttachments(int index)
{ //will not be called }
public void execute() throws Exception {}
}
|
...