Allow easier deployment of endpoints using servicemix-common by splitting
components from endpoints and put all endpoints together
----------------------------------------------------------------------------------------------------------------------------------
Key: SM-532
URL: https://issues.apache.org/activemq/browse/SM-532
Project: ServiceMix
Issue Type: New Feature
Components: servicemix-core
Reporter: Guillaume Nodet
Fix For: 3.1
We could have something like
<sm:container ..>
<sm:activationSpecs>
<sm:activationSpec>
<sm:component>
<http:component ... />
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<jsr181:component ... />
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
<sm:endpoints>
<http:endpoint .. />
<jsr181:endpoint ... />
</sm:endpoints>
</sm:container>
Usually components could be even ommitted when they do not require any specific
configuration.
They could be created on demand somehow when an endpoint is activated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
