> You're probably injecting org.hibernate.classic.Session instead of
> org.hibernate.Session (correct one).
When using org.hibernate.search.impl.FullTextSession you cannot use
the injected org.hibernate.Session because there is an expectation
that the org.hibernate.Session past to the constructor
On Sat, 12 Jun 2010 18:20:34 -0300, Borut Bolčina
wrote:
Render queue error in SetupRender[Index:grid]: Failure reading parameter
'source' of component Index:grid: $Session_1292df1e883 cannot be cast to
org.hibernate.classic.Session
java.lang.ClassCastException
$Session_1292df1e883 cannot be
: tapestry-hibernate grid second page Session is closed
Yes I have:
[INFO] [dependency:tree {execution: default-cli}]
[INFO] com.acme:manager:war:1.0-SNAPSHOT
[INFO] +- org.apache.tapestry:tapestry-hibernate:jar:5.2.0-SNAPSHOT:compile
[INFO] | +- org.apache.tapestry:tapestry-core:jar:5.2.0-SNAPSH
mmit the transaction manually though.
Regards,
Jim.
-Original Message-
From: Borut Bolcina [mailto:borut.bolc...@gmail.com]
Sent: 11 June 2010 19:55
To: Tapestry users
Subject: Re: tapestry-hibernate grid second page Session is closed
Yes I have:
[INFO] [dependency:tree {execution:
The Transaction for the default session (sm.getSession()) is started
automatically. So let tapestry handle the transaction stuff and just
inject Session via constructor instead of HibernateSessionManager and
dont begin a new transaction for the FullTextSession.
Yes I have:
[INFO] [dependenc
Yes I have:
[INFO] [dependency:tree {execution: default-cli}]
[INFO] com.acme:manager:war:1.0-SNAPSHOT
[INFO] +- org.apache.tapestry:tapestry-hibernate:jar:5.2.0-SNAPSHOT:compile
[INFO] | +- org.apache.tapestry:tapestry-core:jar:5.2.0-SNAPSHOT:compile
For the error I am getting - I think I got
I googled the exception and found this:
http://old.nabble.com/CommitAfter-not-working-(-is-back-!-)-(-T5.1)-td26230998.html
Do you have both tapestry-hibernate and tapestry-hibernate-core dependencies?
Josh
On Fri, Jun 11, 2010 at 11:01 AM, Borut Bolčina wrote:
> Hello,
>
> yes, I am querying
Hello,
yes, I am querying in the Grid's event method like so:
Index.tml
==
http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
xmlns:p="tapestry:parameter">
Index.java
==
public class Index {
@Inject
p
> when it happened to me it was because some of the cells in the grid were
> referencing lazily-loaded attributes (sub-entities) of the entity your grid
> is paging on.
Are you querying the database when the paging happens? The session is
opened for the entire request so you shouldn't be getting
load the attributes you need
and still take advantage of the inplace grid nav.
Regards,
Jim.
-Original Message-
From: Jim O'Callaghan [mailto:jc1000...@yahoo.co.uk]
Sent: 11 June 2010 17:42
To: 'Tapestry users'
Subject: RE: tapestry-hibernate grid second page Session is clos
Coincidence I am getting this today also Borut. Someone here may be able to
give you more advice, but when it happened to me it was because some of the
cells in the grid were referencing lazily-loaded attributes (sub-entities) of
the entity your grid is paging on. You can either exclude these
11 matches
Mail list logo
