Yep.  That was it...Tapestry Hibernate Session needs work to play nice within
FullTextSession. 

Workaround is in thread below: 

http://tapestry.1045711.n5.nabble.com/Hibernate-Search-td4446040.html

Also, JIRA already open...

https://issues.apache.org/jira/browse/TAP5-1178

I would add 

1.  Hibernate-Lucene search is one of the hottest (or coolest!) thing out
... this would be a priority 
2.  (and/or) disambiguate session generated by services as a tapestry
creation...to perhaps avoid the confusion.  

Basically, I did this...

1.  First inject the HibernateSessionManager just like you would Session.  

import org.apache.tapestry5.hibernate.HibernateSessionManager;
import org.hibernate.Session;

@Inject
private Session session;
@Inject
private HibernateSessionManager sessionManager;

2.  Use it to get the session (and not wrap just the plain old
session)...the session may be used elsewhere to do usual CRUD, not hibernate
search


FullTextSession fullTextSession =
Search.getFullTextSession(sessionManager.getSession()); 

// instead of 
// FullTextSession fullTextSession = Search.getFullTextSession(session); 







--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/grid-dont-link-hibernate-classic-session-tp5669885p5670148.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to