Reference the TestByteOnly testcase.

Basically the dirty checking in EntityBeanIntercept uses standard equals ... but the value changed check used to detect changed properties checks the byte[] via length and values.

This results in the update with no columns being updated ... when the value set is exactly the same as the current value.

The fix is to incorporate the more strict dirty checking in EntityBeanIntercept ... both for byte[] and char[].

Fixed in HEAD.