|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Ok, I understand.
However, if we have something like:
Session session = (Session) entityManager.getDelegate();
session.doWork(new Work() {
@Override
public void execute(Connection connection) throws SQLException { ... }
});
Shouldn't the "Connection" object inside "work" be unwrapped by default? This was working in Hibernate 3.6 and now every time we want to work directly at JDBC level (using session.doWork), we're getting Hibernate semantics and not JDBC semantics.
Is this the expected behavior for session.doWork()? Should I open a new issue?