Now that we have the builds relatively stable, I'm inching closer to
doing the 1.0.0 release (hurray!). I've running the 4.2 blueprint
compliance tests before doing the actual release. Sadly I'm seeing
more failures than we had last release, so progress has screeched to a
halt again. In particular, we're seeing lots of failures with
exceptions like "Unable to convert value 1.0 to type
java.lang.Boolean". It looks like the CT expects to be able to do
something like
<value type=”java.lang.Boolean”>1.0</value>
and have it work. At the moment this is considered an invalid
conversion. I could add some code into our AggregateConverter to make
the conversion work, but I'm not sure that's the right thing to do.
I've had a look on page 240 of the 4.2 spec, where it talks about the
type conversion, and I can't see anything about converting numbers to
booleans. I'm not sure if I'm misinterpreting what the test is trying
to achieve, or if the test has changed since last time, or if we've
regressed a non-spec conversion. Can anyone who knows this area shed
any light?
Holly
