Is there any special reason why we not just allow users to set SessionEventListenerConfig
on Configuration and then get all it's listener and build a new one at buildSessionFactory time ?
That would keep the type safety instead of the typeless setListener(String type, Object listener).
/max
Hi guys,
The configuration of SessionEventListenerConfig was changed recently to avoid users to mutate it after session factory creation.
This broke hibernate console (only swing version at the moment, but mainly the build :).
I can see there is a "TODO: ugh!" in the now new setListener() in Configuration
which I could use instead to configure it programatically.
Does anyone have any thoughts on what that "TODO: ugh!" should be replaced with ?
I would like to at least add constants for all those types of even listener
simply to avoid "mis-types" because there sure is *alot*!
But before i'll go do that - anyone with info on the TODO ? ;)
-- Max Rydahl Andersen callto://max.rydahl.andersen
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
