Is there any earthly reason why a stateless session does not allow interceptors?

The StatelessSessionImpl constructur is hardcoded to use an empty interceptor.

Hm, I tried and modified the source code, so that StatelessSessionImpl has an overloaded constructor that takes an interceptor. I also modified the session factory, so that it provides access to this constructor.

For my case it is working nicely: Adjusting the generated sql in onPrepareStatement(). This is to redirect inserts to an inherited table - which is postgres's way of partitioning. There are other ways to do this in the db directly (rules or triggers), but those ware way slower.

Can this be made part of Hibernate itself?

only reason currenlty is that most of the operations on Interceptor does not make sense for Stateless session.

put a request in jira for your usecase...

Thanks a lot for the answer.
I've done that:
http://opensource2.atlassian.com/projec ... e/HHH-1497

i feel requirement to have new instamce of interceptor per session is not un common. For e.g if audit using interceptor api is to be done in managed environment then we have no existing api to support this.

We need to overload getCurrentSession() method, to accept Interceptor. Reaosn is say in audit, we need to pass userId. auditID, userComment to be available to call back methods of interceptor.
MyInterceptor interceptor = new MyInterceptor("userId");
Session session = SF.getCurrentSession(interceptor);
DAO.method( session);
session.flush()

In the callback methods onSave or postFlush userID will be available.

Whats the use of putting it on JIRA
http://opensource.atlassian.com/project ... e/HHH-1497
so it stays there unfixed for years.

Then fix it and send the patch.