If you ever have doubts whether some VM parameters are affecting your
test execution, I think you might be able to add a call to
http://java.sun.com/j2se/1.5.0/jcp/beta1/apidiffs/java/lang/management/RuntimeMBean.html#getInputArguments()
to see what VM parameters have been passed to your test.
We are not proxying SessionImplementor but only Session.
so we would need to
- proxy SessionImplementor and Session
- whitelist getListeners
I don't see any issue to that. If nobody objects we can move forward.
On 4 janv. 2010, at 01:16, Sanne Grinovero wrote:
> Hello All,
> when binding the S
What problems does it lead to?
As per the doc, "loaded" means the reference is consistent with the DB state, a
new or deferenced collection is by definition not consistent.
On 24 déc. 2009, at 16:47, Florent Bayle wrote:
> Hi,
>
> While testing one of our app, I found a problem : after saving
Hi,
just checked that it is already proxying all of:
org.hibernate.classic.Session.class,
org.hibernate.engine.SessionImplementor.class,
org.hibernate.jdbc.JDBCContext.Context.class,
org.hibernate.event.EventSource.class
so the
First, this code does not build on the JPA 2 metamodel. It was started
actually before JPA 2 was started. It does however share some similar
concepts with the JPA 2 metamodel which I suggested we should leverage.
Of course the JPA 2 metamodel makes the assumption that the object model
is what we
