[
http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12357599 ]
Rex Sheridan commented on JBESB-437:
------------------------------------
I don't really understand how ConfigTree().childPropertyList() would solve the
problem. ConfigTree is a pull based configuration approach as opposed to a push based
one. I simply want my action class to look like the following:
class MyAction {
private String someProp;
private int count;
public Message process(Message message) throws Exception {
....
}
public void setSomeProp(String val) {
this.someProp = val;
}
public void setCount(int val) {
this.count = val;
}
}
And the configuration would look similar to:
<action name="anAction" class="MyAction">
<property name="someProp" value="foo"></property>
<property name="count" value="5"></property>
</action>
Notice how MyAction doesn't take a ConfigTree in its constructor. Its values are
populated automatically just by following JavaBean conventions.
Beans based configuration option for actions
--------------------------------------------
Key: JBESB-437
URL:
http://jira.jboss.com/jira/browse/JBESB-437
Project: JBoss ESB
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: Configuration
Reporter: Rex Sheridan
Assigned To: Kevin Conner
Priority: Minor
Fix For: 4.2 Milestone Release 2
Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java,
BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java,
NotifyFTP.java
This is a first pass at a beans based configuration approach for actions and notification
targets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira