Yes makes sense.
On 23 oct. 09, at 21:32, Sanne Grinovero wrote:
> No Similarity is not being read from configuration files, just the
> annotations.
> Current behaviour already throws an exception if two/more entities
> from the same class hierarchy define a different Similarity, but in
> this
Hi,
I agree with Emmauel. Warnings are too weak. I think in the case where two
entities share the same index,
but only one defines explicitly a Similarity an exception should be thrown.
Regarding the configuration - I also feel there are several
inconsistencies. As Sanne is saying the
problem
