activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Niski <>
Subject Re: AMQ 5.4.2 schema validation and Spring PropertyPlaceholderConfigurer
Date Fri, 28 Jan 2011 22:19:48 GMT
Sure - i just found your (Gary's) comments re:numeric values in

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:

thanks again,

Joe Niski
IS Development |  NWEA

PHONE 503.548.5207  |  FAX 503.639.7873

NWEA.ORG<3D%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
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?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message