Problems when setting an integer value by PropertyPlaceHolderConfigurer

[Ryan Flegel]

Hey,

I'm running into a problem that I believe to be the exact same as the one found here:
http://forum.springsource.org/showth...lderConfigurer

However, the attribute I'm having trouble with is tx:annotation-driven's order. It is defined in the schema as an xsd:int. I guess this causes the SAX parser to choke before PropertyPlaceholderConfigurer has a chance to replace the property placeholder.

Caused by: org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${AopConfiguration.transaction}' is not a valid value for 'integer'.

Should "order" be a string instead? Is there anyway to work around this limitation?

--
Thanks,
Ryan

[dr_pompeii]

Read the other post, such bug is not related with Spring.

[Ryan Flegel]

It is related to Spring. It's the tx schema that I'm having trouble with:

http://www.springframework.org/schem...ing-tx-3.0.xsd

[Marten Deinum]

Although it is related to spring it isn't going to be fixed. The problem is do you want xsd validation or do you want support for property placeholder. In the latter case each and every property would have to be a string, which basically reduced or disables the reason why there are xsd in the first place. So in short the xsd isn't going to be changed.

There is a workaround this, however, requires some work on your side. You would have to disable schema validation this can be done by implementing your own ApplicationContext (extending the current ones) and use those in your application. That way there is no more schema validation and that should enable the property place holder stuff.

[Ryan Flegel]

Thanks, Marten. You've pretty much confirmed what I expected.

In my case, it's not worth disabling schema validation for, but it would have been nice to have.