Christian,
I don't think it has anything to do with the AbstractBeanDefinitionParser. It
has to do with the schema validation that we turn on by default and camel
doesn't. The schema validation occurs at XML parse time when spring is
constructing the DOM. This is long before any of the spring bean
processing.
The issue is types that aren't strings really don't validate with properties.
For example, a <element name="timeout" type="int"/> won't validate if it
appears as:
<timeout>${cnfigured.timeout}</timeout>
in the xml file as that's not an int.
If you turn off the schema validation, it will probably work for you.
Obviously, you have to make sure the xml is then valid yourself. I think it
would be -Dorg.apache.cxf.spring.validation.mode=VALIDATION_NONE
Dan
On Saturday 13 September 2008 7:20:16 pm Christian Schneider wrote:
> Hi,
>
> currently the cxf spring configurations like <jms:conduit> use the
> AbstractBeanDefinitionParser. As far as I understand it this parser does
> not support
> spring´s PropertyPlaceholderConfigurer. Is that correct?
>
> I think for many people externalising some configuration settings from
> the spring application context into property files is extremely
> important. Is there an easy way to achieve this?
> Camel does not have this problem as far as I know.
>
> Greetings
>
> Christian
--
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
