[
https://issues.apache.org/jira/browse/TAP5-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263606#comment-13263606
]
Uday Kari commented on TAP5-1178:
---------------------------------
Perhaps, disambiguate hibernate session generated by services as a tapestry
creation..?
This also would allow co-existence with hibernate core and also avoid users to
think they have a hibernate session when in fact they have a tapestry hibernate
session.
Specifically,
import org.apache.tapestry5.hibernate.Session;
and, instead, make
import org.hibernate.Session;
look for hibernate-core.
This would relieve Tapestry of the burden to play catch-up with hibernate.
> Tapestry should include a module that automatically configures for Hibernate
> Search
> -----------------------------------------------------------------------------------
>
> Key: TAP5-1178
> URL: https://issues.apache.org/jira/browse/TAP5-1178
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-hibernate
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
>
> It's common to use Hibernate Search (based on Lucene) on top of Hibernate
> itself. To make this work in Tapestry requires some careful overrides in
> order to create and manage a FullTextSession instance, rather than a standard
> Session instance. However, its not much code.
> This could be in the form of a code donation from work I'm performing for a
> client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
