Thanks for the hint.
Although I'm not sure how this problem is related to validation. In my
case ${service.port} is simply not resolved - there are no XML/bean
validation errors.
Cheers,
Szczepan
On Tue, Oct 20, 2009 at 3:46 PM, Brent Verner <[email protected]> wrote:
> Hi,
>
> If you're loading the configuration yourself, you can subclass the
> appropriate ApplicationContext to disable validation...
>
> public class NonValidatingClassPathXmlApplicationContext
> extends ClassPathXmlApplicationContext {
> public NonValidatingClassPathXmlApplicationContext(String
> conf) {
> super(conf);
> }
> protected void initBeanDefinitionReader(
> XmlBeanDefinitionReader
> beanDefinitionReader) {
> super.initBeanDefinitionReader(beanDefinitionReader);
>
> beanDefinitionReader.setValidationMode(XmlBeanDefinitionReader.VALIDATION_NONE);
> beanDefinitionReader.setNamespaceAware(true);
> }
> }
>
>
> hth.
> Brent
>
> On Tue, Oct 20, 2009 at 8:41 AM, szczepiq <[email protected]> wrote:
>> Hi,
>>
>> Following the wiki entry:
>> http://cwiki.apache.org/CXF20DOC/jetty-configuration.html
>>
>> There is any example:
>>
>> <httpj:engine-factory bus="cxf">
>> ...
>> <httpj:engine port="9001">
>> ...
>>
>> How can I make the engine *port* configurable via Spring property
>> placeholders?
>>
>> I tried following:
>>
>> <httpj:engine port="${service.port}">
>>
>> However, it doesn't work. I can understand why it doesn't work:
>> httpj:engine is a schema extension, not a typical bean wiring stuff
>> where property placeholders work out of the box.
>>
>> The question is how can I make it working so that I can configure the
>> port via a property?
>>
>> Thanks!
>> Szczepan
>>
>
