Currently JdbcValueHandler.BlobJdbcValueHandler will accept byte arrays and 
Blobs (reluctantly) but not ByteBuffers.  The problem is that the service 
engine uses ByteBuffer as the attribute type for attributes created based on 
blob entity fields and crud services fail due to this because they don't 
attempt to convert them before using something like <create-value/>.

So what is the correct behavior?  Should the service engine be using a 
different type or should the JdbcValueHandler be more flexible?

Thanks
Scott

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to