It potentially changes every minor release (in particular the internal
interfaces like SessionImplementor that we need to implement).
One of the benefits is that an old version of HSearch would work with the
latest version of Hibernate Core including the new methods and we would not
have to mai
Actually I've never had this problem. Admittedly after reading your email
I did a quick
check and I get also a compilation error due to 'isReadOnly' not being
overridden.
Does Session really change that often that we have a use of a dynamic
proxy? Would it
not be easier to not depend on a SN
Guys,
I am sick of HSearch being broken every time Core adds a new method to Session
/ SessionImplementor and the like.
I am seriously thinking about providing a dynamic proxy implementing FTSession
etc and will try and prototype it.
Any opinion?
___
