>>> Is that ok / preferable if I do these type checking at the bridge creation
>>> time - in the BridgeProvider.
>>
>> Not sure. AS you say, the problem is if you define the type as Object.
>> Probably quite uncommon.
>
> I'd enforce it. If a getter guarantees to provide a refined type, it
> c
On 2 April 2014 19:42, Hardy Ferentschik wrote:
>
> On 2 Jan 2014, at 18:30, Emmanuel Bernard wrote:
>
>> Hardy,
>>
>> Today the actual bridge fails during set() if the object passed is not of a
>> specified subset of types (Blob, etc).
>
> Right, that happens in TikaBridge#getInputStreamForData
On 2 Jan 2014, at 18:30, Emmanuel Bernard wrote:
> Hardy,
>
> Today the actual bridge fails during set() if the object passed is not of a
> specified subset of types (Blob, etc).
Right, that happens in TikaBridge#getInputStreamForData
> This means the failure happens at the first indexing us
Hardy,
Today the actual bridge fails during set() if the object passed is not of a
specified subset of types (Blob, etc).
This means the failure happens at the first indexing usage.
Is that ok / preferable if I do these type checking at the bridge creation time
- in the BridgeProvider. The only
