cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From loadmanc <chris.load...@gmail.com>
Subject HttpConduit "name" - Ability required to inject a property for the http:conduit name attribute
Date Thu, 28 Jul 2011 07:15:22 GMT
I have tried everything to try and inject a value from a property file into
the http:conduit name attribute. I would like to do something like
<http:conduit name="${property}">. I also had a look at the HTTPConduit
class and realise that there is only a getter, but no setter for
HTTPConduit.conduitName.

I do not want to hard code the http:conduit name value as we have different
environments that require different values to be in the name field,
depending on which environment we are running (eg. test or production)

Is there any specific reason that this is the way it is. A solution to this
would be a great help, as we can currently inject properties for all other
attributes, or properties but the only one we have to hard code is the
http:conduit name. This is annoying as if we need to change the endpoint
when deployed in a production/test environment, we need to modify the
applicationContext and reseploy rather than just get the web admins to
change a property in an external file.

Many thanks,

Chris.

--
View this message in context: http://cxf.547215.n5.nabble.com/HttpConduit-name-Ability-required-to-inject-a-property-for-the-http-conduit-name-attribute-tp4641515p4641515.html
Sent from the cxf-issues mailing list archive at Nabble.com.

Mime
View raw message