The session isn't closed until you are leaving the request, after your
template has rendered. The problem is most likely with your query or
your data. Try accessing the values from your component class and you
should see that it's still null.
You should also enable logging for hibernate to see exa
My mapping are ok, because yesterday I used eager fetching on all collections
and it worked, I just removed every eager mappings and create criteria for
all one level criteria, problem is when I try to go deeper...
It seams that problem is that session is closed when I try to fetch data...
It see
Hi,
You should check your mapping to be sure the many-to-one relationship
between "comment" and "user" is correct, and verify your database table
"comment" contains an existing foreign key to the user table.
Best thing to do is to run your Criteria in a JUnit test.
Nicolas.
Bojan Cincur a
Hi,
Looks more like an issue with your criteria. Have you tried to use
FetchMode.EAGER instead?
Christian
Bojan Cincur schrieb:
Hi all,
I have a little problem.
I'm using hibernate criteria to fetch list of objects that I want to display
in loop component. (enclosed in my commentModule co
you shouldn't persist any object from hibernate
@ApplicationState
private Customer _customer;
same object will be referenced in you second request,
and the second request will have different session,
tapestry-hibernate integration is still basic,
and for now you should just change
