Sure - i just found your (Gary's) comments re:numeric values in https://issues.apache.org/jira/browse/AMQ-2939.
i agree that assuring type-safety is a good reason for schema validation, but an exception will get raised anyway if a value unacceptable to the code (i.e., a string that doesn't represent a boolean value) is passed in, so we're not losing much. For now, we can either hard-wire the value or disable validation, depending on what our security and operations folks prefer. Here's the issue: https://issues.apache.org/jira/browse/AMQ-3168 thanks again, Joe Joe Niski IS Development | NWEA PHONE 503.548.5207 | FAX 503.639.7873 NWEA.ORG<3D%22http://www.nwea.org/%22> | Partnering to Help All Kids Learn On 01/28/2011 01:11 PM, Gary Tully wrote: the only way around this is to change the schema such that the value is a string rather than a boolean and have a string to boolean converter. This reduces the type safety of the schema but does mean that the property placeholder can work. We have changed most/all of the numeric values to String for this reason (adding an annotation for the Xbean schema generator), I guess we can do it for booleans also. Want to raise a jira issue for this?
