--- On Sat, 9/18/10, Scott Gray wrote:
> On 13/09/2010, at 12:09 PM, Adrian
> Crum wrote:
>
> > --- On Sun, 9/12/10, Scott Gray
> wrote:
> >> On 12/09/2010, at 2:57 AM, Adrian
> >> Crum wrote:
> >>
> >>> --- On Sat, 9/11/10, Scott Gray
> >> wrote:
> Currently
> JdbcValueHandler.BlobJ
On 13/09/2010, at 12:09 PM, Adrian Crum wrote:
> --- On Sun, 9/12/10, Scott Gray wrote:
>> On 12/09/2010, at 2:57 AM, Adrian
>> Crum wrote:
>>
>>> --- On Sat, 9/11/10, Scott Gray
>> wrote:
Currently
JdbcValueHandler.BlobJdbcValueHandler will accept
>> byte
arrays and Blobs (reluc
--- On Sun, 9/12/10, Scott Gray wrote:
> On 12/09/2010, at 2:57 AM, Adrian
> Crum wrote:
>
> > --- On Sat, 9/11/10, Scott Gray
> wrote:
> >> Currently
> >> JdbcValueHandler.BlobJdbcValueHandler will accept
> byte
> >> arrays and Blobs (reluctantly) but not
> ByteBuffers.
> >> The problem is tha
On 12/09/2010, at 2:57 AM, Adrian Crum wrote:
> --- On Sat, 9/11/10, Scott Gray wrote:
>> 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
--- On Sat, 9/11/10, Scott Gray wrote:
> 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 a
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 do
