At some point we might add that for convenience. But I would really
avoid any build time *requirement* on core features.
baliuka juozas wrote:
Yes, I mean build time transformation. We use it for
lazy propeties anyway. Domain object can implement
HibernateProxy interface itself, it must be tri
Yes, I mean build time transformation. We use it for
lazy propeties anyway. Domain object can implement
HibernateProxy interface itself, it must be trivial to
integrate without changes in framework.
--- Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
> You mean build time transformation?
>
> baliuka
You mean build time transformation?
baliuka juozas wrote:
Probably class file transformation can help. I can do
it if it is usefull. It is more trivial to implement
this kind of persister than proxies and it will be
more performant.
--- Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
I've imp
Probably class file transformation can help. I can do
it if it is usefull. It is more trivial to implement
this kind of persister than proxies and it will be
more performant.
--- Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
> I've implemented the warning message when a class
> use final
> getters
I've implemented the warning message when a class use final
getters/setters. But this will correctly work only for the
PropertyAccessor method. In this cass its more an error message.
The basic problem is that a class can have final methods, but the object
state has to be accessed through a no