[
http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12359282 ]
Derek Adams commented on JBESB-437:
-----------------------------------
I checked the bean config code into the trunk today. The code works as mentioned above,
but with one addition. To be processed as a bean configured action, the action should
implement the marker interface org.jboss.soa.esb.actions.BeanConfiguredAction. This just
lets the action processing pipeline know to process it differently. I updated the
org.jboss.soa.esb.actions.persistence.StoreMessage as an example.
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: Rex Sheridan
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