Hello,
we are using Hibernate for about 8 months now, 2 of those even in production, and didn't have any problems with it at all.
But recently I encountered the following issue (I don't know if its my fault or a bug).
I am using the criteria API for a search screen (multiple tables are involved, restrictions may be applied to one or more of them).
We are using FetchMode.JOIN for all of the needed tables (no lazy initialization is wanted).
Basically the search screen works already, data is retrieved and displayed correctly.
However, I had to add an restriction to a table which was previously only fetched but had no restrictions on itself.
Then I added an alias for the path in the criteria object.
After doing this I recompiled and tried the new screen, the result was that I encountered an LazyInitializationException in the already working code.
It seems that adding the alias changed the generated SQL and the FetchMode is being ignored.
I even tried to change the association path in the fetchmode for the entity to the alias name which resulted in a SQLGrammarException.
Because we are using an older version of Hibernate (from december last year) I upgraded Hibernate to 3.1.3 on my workstation but the problem still occurs.
Sorry to bother you with this issue if its a no brainer but I already spent some time on Google and reading in our books on this problem and didnt find a solution for it.

kind regards & thanks in advance, Christian

Hi,
I could solve the problem by myself.
Instead of using

I now use

whith Join Type

.
kind regards, Chris