On 05 Feb (14:48), Ugo Cei wrote:
> public Serializable save(Object obj) {
> // Do something before saving ...
Thats the job of an Interceptor?
--
Christian Bauer
[EMAIL PROTECTED]
http://www.hibernate.org/
---
The SF.Net email is spon
Emmanuel wrote:
It seems to me that it's not a common case at all
Of course it's not that common. If it were, maybe someone else would
have solved this problem by now :-).
My use case is as follows: I need to add behavior to a Session's save,
update, saveOrUpdate methods. As things stand, I can
It seems to me that it's not a common case at all. I'm intend believe it
has more drawbacks to "pollute" the public API with such a need than
stay that way.
Ugo Cei wrote:
[I'm reposting this message since it didn't get any attention the
first time I did (more than 2 months ago). Maybe people
[I'm reposting this message since it didn't get any attention the first
time I did (more than 2 months ago). Maybe people were too busy at the
moment, or maybe this issue is not that interesting, in which case
please excuse me.]
Hi,
for an application I'm writing, it would be useful to extend
Hi,
for an application I'm writing, it would be useful to extend the
functionalities of the Session interface via inheritance, with a class
that either "implements Session" or "extends SessionImpl".
Unfortunately, if I'm not mistaken, the Configuration class is hardwired
to return an instance
