You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2007/03/13 22:37:34 UTC
[jira] Resolved: (SM-532) Allow easier deployment of endpoints
using servicemix-common by splitting components from endpoints and put all
endpoints together
[ https://issues.apache.org/activemq/browse/SM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SM-532.
--------------------------------
Resolution: Fixed
http://svn.apache.org/viewvc?view=rev&revision=517876
http://svn.apache.org/viewvc?view=rev&revision=517877
http://svn.apache.org/viewvc?view=rev&revision=517881
> 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
> Assigned To: Guillaume Nodet
> Fix For: 3.2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.