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 SNAPSHOT in the pom. We could depend on
the latest 3.5
beta. You still have to implement the missing methods in FullTextSession
when you do
an upgrade, but the process is more controlled.
Are there any other benefits of a dynamic proxy?
--Hardy
On Wed, 13 Jan 2010 12:07:48 -0300, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
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?