WARN Validation - Validation errors validating a 'DataSource'

[jay.l.fisher]

During startup as our data sources are being loaded I see this warning logged to the Eclipse console.

=== 2011-01-21 08:26:45,038 [l0-2] DEBUG ValidationContext - Adding validation errors at path '/DataSource[@ID=IPCLASS]/fields/field[@name=CSRK]/validators/validator/max': {errorMessage=Must be a whole number.}
=== 2011-01-21 08:26:45,040 [l0-2] DEBUG ValidationContext - Adding validation errors at path '/DataSource[@ID=IPCLASS]/fields/field[@name=CSRK]/validators/validator/min': {errorMessage=Must be a whole number.}
=== 2011-01-21 08:26:45,042 [l0-2] DEBUG ValidationContext - Adding validation errors at path '/DataSource[@ID=IPCLASS]/fields/field[@name=CMKP]/validators/validator/max': {errorMessage=Must be a whole number.}
=== 2011-01-21 08:26:45,044 [l0-2] DEBUG ValidationContext - Adding validation errors at path '/DataSource[@ID=IPCLASS]/fields/field[@name=CMKP]/validators/validator/min': {errorMessage=Must be a whole number.}
=== 2011-01-21 08:26:45,044 [l0-2] WARN  Validation - Validation errors validating a 'DataSource':
{
    "/DataSource[@ID=IPCLASS]/fields/field[@name=CMKP]/validators/validator":{
        recordPath:"/DataSource[@ID=IPCLASS]/fields/field[@name=CMKP]/validators/validator",
        max:{
            errorMessage:"Must be a whole number."
        },
        min:{
            errorMessage:"Must be a whole number."
        }
    },
    "/DataSource[@ID=IPCLASS]/fields/field[@name=CSRK]/validators/validator":{
        recordPath:"/DataSource[@ID=IPCLASS]/fields/field[@name=CSRK]/validators/validator",
        max:{
            errorMessage:"Must be a whole number."
        },
        min:{
            errorMessage:"Must be a whole number."
        }
    }
}

It has been showing up for a very long time and does not seem to have an adverse effect on anything, but we're getting the app ready for production deployment and want to clear up as many of these small mysteries as possible.

Any ideas what would cause this? Here is the ds.xml definition of the two data source fields in question.

<field name="CSRK" title="Shrinkage Factor" type="float" detail="true">
	<validators>
		<validator type="floatRange" min="0.000" max="0.999"
			errorMessage="Please enter a positive number between zero and .999." />
		<validator type="floatPrecision" precision="3"
			errorMessage="The maximum number of decimal places is 3" />
	</validators>
</field>
<field name="CMKP" title="Desired Markup" type="float" detail="true">
	<validators>
		<validator type="floatRange" min="0.000" max="0.999"
			errorMessage="Please enter a positive number between zero and .999" />
		<validator type="floatPrecision" precision="3"
			errorMessage="The maximum number of decimal places is 3" />
	</validators>
</field>

It appears that something doesn't like the decimal point in the min and max attributes. If I change it to min="0" I only get warnings about the max validator. The field is defined in the database as a DECIMAL(3, 3) and we need to insure it is not a negative number. Is there a better way to format the min/max values for a float type field?