Funnilly, pam just felt into the binary trap trying to search for a Jpeg photo from the server, and get some badly decoded binary for this image, just because it was not seen as binary thus stored as a UTF-8 String into the server, instead of storing it as byte[].
Obviously we must fix that by correctly handling binary attributes into the Schema interceptor, and not in the codec :) Oh, it's supposed to work if we fix the server.xml file, btw... On 12/8/06, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
On 12/8/06, Alex Karasulu <[EMAIL PROTECTED]> wrote: > > Emmanuel Lecharny wrote: > > > I guess we can relax a little bit the decoder checks by > > considering that > > > all attribute values are byte[], and let the Schema Interceptor > deal > > > with badly written values, checking them with their associated > > Syntax. > > > > > > wdyt ? > > > > > > IMO it is not required to check for syntax if the attribute is > binary. > > > > > > not true. Jpeg is binary, but it has a special syntax... > > Yeah but if it's binary we just treat it as a blob. The point is that we _know_ it's binary because we know it's attribute Type, so we don't need to keep a set of binary attributes. Why should we go > above and beyond a database to make sure we validate blobs? We won't validate blobs. Alex > > > > -- Cordialement, Emmanuel Lécharny
-- Cordialement, Emmanuel Lécharny
