#x27;t in 3.2.5 and below, and with my
> proposed fix, it wouldn't be there in the future, and would be 100%
> backwards compatible. Sounds like a pretty sweet deal to me ;)
>
> On Thu, Jun 19, 2008 at 5:32 PM, joël Winteregg
> <[EMAIL PROTECTED]> wrote:
> > Hi Les,
&g
Hi Les,
I also had the same issue which was fixed using an update of the
transaction manager I use (Bitronix 1.3). A light JNDI server is now
embedded in it...
For info, the main developer of Bitronix is also working for Atomikos
(JTA world seems to be small ;-)
My JNDI hibernate.cfg.xml is now
Hi Chris,
> > As I understood from your post on issue HHH-3110, Hibernate should not
> > use a lookup class anymore but create (instance) the Transaction
> > Manager. Am I right ? If so, to do this, I should implement a
> > org.hibernate.transaction.TransactionFactory for my transaction
> > manage
Hello Chris,
Thanks for your email. As you will notice I posted a related question on
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3110 this
morning.
>
> I haven't looked closely enough to comment on the query problem but I
> can confirm that your assessment above is correct.
Dear hibernate-dev,
After mnnny googling and after someone told me (through an IRC chat)
that this problem could be a bug, I finally come to you..
Explanations are given here:
http://forum.hibernate.org/viewtopic.php?p=2379177
This behavior is related to polymorphic Criteria queries using a
