On 2 Jan 2014, at 18:30, Emmanuel Bernard <emman...@hibernate.org> 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 usage. Correct > 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. > It seems like a small flexibility loss and we would gain clearer error > messages: if something is annotated @TikaBridge and we don’t support the type > we will fail fast. Fail fast sounds good. —Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
