[
https://jira.jboss.org/jira/browse/JBESB-2270?page=com.atlassian.jira.plu...
]
Richard Burton commented on JBESB-2270:
---------------------------------------
Kevin, I recently started to dig deep into the code base in an effort to create some
improvements and then I came across this issue.
There's a few items I believe would greatly improve the usability of JBoss's ESB
which I've listed below (A locally I'm working on patches which I'll send
over).
An ActionPipelineProcessor should be configured by default via the invocation of the
setter methods without having the developer implement BeanConfiguredAction. Required
attributes could be identified by using Annotations. e.g., @Required. Defaulting to this
behavior will greatly improve the tooling support from within Eclipse, since now
reflection can be used to discover what attributes are configurable and which ones are
required dynamically. Secondly, it prevents the need for a constructor that accepts
ConfigTree to pull the various attributes need for the Action.
An abstraction for the construction of the ActionPipelineProcessors should be created
within the engine itself. There's a fairly strong dependency on
ActionProcessorMethodInfo and the various static methods for the construction of
ActionPipelineProcessors, which if abstracted would allow better control and flexibility
over the ActionPipelineProcessor creation. I would love to greatly improve upon the Spring
integration.
Lastly, I have create a pom to build the Rosetta ESB project using Maven. The XMLBeans
creates the various generated classes as well and I've identified (but I need to
verify) all of the dependency versions used in the project. There's only JARs which
I've referenced using the systemPath since those jars are no where to be found in the
Maven Central Repository. e.g., FTP Server 1.0 incubator for Apache which is used for test
cases only. I strongly recommend building the project using Maven since this will ease the
building of the various *.esb and *.sar projects developed those using Maven.
If you're interested in any of the patches I am working on, please feel free to
contact me.
Richard L. Burton III
Provide an alternative for bean configured action
-------------------------------------------------
Key: JBESB-2270
URL:
https://jira.jboss.org/jira/browse/JBESB-2270
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Reporter: Kevin Conner
Fix For: 4.x
The bean configured action code has a number of deficiencies which include the following
- instantiation of the action per message
- no support for standard callbacks (including lifecycles)
We should create an alternative which creates a single instance of the action, configures
properties through reflection and also supports the standard callback methods.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira