[
http://jira.jboss.com/jira/browse/JBESB-1081?page=comments#action_12378354 ]
Tom Fennelly commented on JBESB-1081:
-------------------------------------
If I could suggest something else we might be able to do....
The deployer could check the actions configured in the jboss-esb.xml and do the same for
other .esb dependencies e.g. if any of the CBR based actions are used, add a dependency on
jbrules.esb... if the SmooksTransformer is used anywhere, add a dependency on smooks.esb
etc This wouldn't be too hard to do (I think) and would make things a lot more
reliable.
You could do it based on a list in a .properties file somewhere e.g.
org.jboss.soa.esb.actions.converters.SmooksTransformer.dependecy=jboss.esb:deployment=smooks.esb
org.jboss.soa.esb.actions.soap.SOAPClient.dependency=jboss.esb:service=SoapUIClientService
etc...
Make jbossesb.esb dependency implicit
-------------------------------------
Key: JBESB-1081
URL:
http://jira.jboss.com/jira/browse/JBESB-1081
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Configuration
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.1 IR1
Every esb has an implicit dependency on the core jbossesb.esb service. We should have
the deployer enforce this dependency instead of requiring an explicit declaration.
--
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