Rainer wrote : sorry for the panic, but I was working against the clock and
willing to take any humiliation connected with stupid questions :-)
I would say you deserve bonus points instead of humiliation ;-)
Cheers,
Koen
View the original post :
Rainer wrote : You missed out on a case of beer though.
This is a pity though... Our thirst is legendary ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3919515#3919515
Reply to the post :
I've isolated the problem.
Just creating the Query
select pl from org.jbpm.logging.log.ProcessLog as pl where pl.token = :token
order by pl.index
(this is from LoggingsSession.findLogsByToken() ) already throws a
HibernateException: instance not of expected entity type:
This one was bizarr!
Hibernate does an autoflush when createQuery is called (I don't know if this
always happens but in this case it did and to find out I had to trace 15
stacklevels of Hibernate code)
As I have some 'transient' objects in the current processInstance (I remove
them before
Rainer,
You are truely a champion in solving your own problems! Anyway it is great that
you keep us posted on your struggles.
Thanks a lot and regards,
Koen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3919433#3919433
Reply to the post :
by default hibernate will flush before it executes a query. that is normal
cause the modified data related to your session could be involved in the query.
and the query is executed in the db. that's why hibernate has to flush at
query time.
anyways. some very impressive digging !
is there
Hi guys,
sorry for the panic, but I was working against the clock and willing to take
any humiliation connected with stupid questions :-) Speed was all that mattered.
What surprised me was that it was tested code that threw up this problem. I was
just playing around with some very rare
