You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Stefan Lecho (JIRA)" <ji...@apache.org> on 2008/09/18 22:02:44 UTC
[jira] Commented: (SYNAPSE-385) Externalize environment specific
variables from xml definition files
[ https://issues.apache.org/jira/browse/SYNAPSE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632361#action_12632361 ]
Stefan Lecho commented on SYNAPSE-385:
--------------------------------------
It would be nice if this could be implemented based on the Spring PropertyPlaceHolderConfigurator.
> Externalize environment specific variables from xml definition files
> --------------------------------------------------------------------
>
> Key: SYNAPSE-385
> URL: https://issues.apache.org/jira/browse/SYNAPSE-385
> Project: Synapse
> Issue Type: New Feature
> Environment: Any
> Reporter: Tanmay saha
>
> Synapse should allow user to externalize environment specific variables (like hostname, port number in endpoint definition ) into some property file or JNDI store and then refer in endpoint definition as
> <endpoint xmlns="http://ws.apache.org/ns/synapse">
> <address uri="http://<b>${hostname}:{port}</b>/soap/SimpleStockQuoteService"/>
> </endpoint>
> Without this feature config meta data needs to be updated for enviroment related variables while deploying the same artifact in DEV --> QA -->UAT -->PROD.
> In Sox compliance world it will be a violation to change something in the artifact which has already been deployed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org