Thanks Thiago, I'll run it by the hibernate-search team next.
On Wed, Feb 12, 2014 at 12:59 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> I'd check the Hibernate Search part. The stack trace doesn't look like a
> Tapestry issue to me.
>
>
>
I'd check the Hibernate Search part. The stack trace doesn't look like a
Tapestry issue to me.
On Wed, 12 Feb 2014 15:02:32 -0200, George Christman
wrote:
Hi Guys, I'm seeing the following exception in my logs when I try to
start
my app. It appears to be random and only
what it means. Could
this be an order of operation causing this? I'm not sure if it's something
I have configured wrong in Tapestry or if it's a hibernate-search bug.
Thanks
/**
*
* @param sessionManager
*
* @return
*/
@Scope(ScopeConstants.PERTHREAD
This would also work (and would only happen at most once per request:
@Scope(ScopeConstants.PERTHREAD)
public static FullTextSession buildFullTextSession(HibernateSessionManager
sessionManager) {
return Search.getFullTextSession(sessionManager.getSession());
}
Seems like it's caused by your jvm's security and accessing a private class.
This should work (less verbose too):
public static FullTextSession buildFullTextSession(
final HibernateSessionManager sessionManager,
PropertyShadowBuilder propertyShadowBuilder)
{
Hi, Lance Java offered the following snippet of code back in
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/grid-dont-link-hibernate-classic-session-td5669885.html
--
You could add this to your app module:
private static class LazyFullTextSession {
private Hibern
Interesting...thanks, Lance. Probably improves performance in search results
page loading.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/grid-dont-link-hibernate-classic-session-tp5669885p5671534.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
You could add this to your app module:
private static class LazyFullTextSession {
private HibernateSessionManager sessionManager;
public LazyFullTextSession(HibernateSessionManager sessionManager)
{
this.sessionManager = sessionManager;
}
publi
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
haus.org
>
>
>
>
>
> 2011/6/1 Mark :
>> I'm working on a project where I want to user Hibernate-Search (uses
>> lucene queries and analyzers for stemming, etc.). However, it appears
>> that the session I'm getting from tapestry-hibernate is different
>> e
extSession(sessionManager.getSession());
}
with regards
Sven Homburg
Founder of the Chenille Kit Project
http://chenillekit.codehaus.org
2011/6/1 Mark :
> I'm working on a project where I want to user Hibernate-Search (uses
> lucene queries and analyzers for stemming, etc.). However,
I'm working on a project where I want to user Hibernate-Search (uses
lucene queries and analyzers for stemming, etc.). However, it appears
that the session I'm getting from tapestry-hibernate is different
enough that I can't use it to create a FullTextSearch.
https://issues.
<https://mail.google.com/>I ran into this problem over the weekend.
FullTextSessionImpl<http://fisheye.jboss.com/browse/Hibernate/search/trunk/src/java/org/hibernate/search/impl/FullTextSessionImpl.java?r=12806>casts
the passed session to
SessionImplementor<http://fisheye.j
make a per thread service with the session inside,
get it from that service. then it will work for hibernate-search.
>
> public static SessionFactory buildSessionFactory(){
> SessionFactory sessionFactory=null;
> try {
>
ionFactory ){
return sessionFactory.openSession();
}
I have looked into the code of FullTextSessionImpl in hibernate-search.
Do you know why they are casting between org.hibernate.Session to
org.hibernate.classic.Session?
Thanks a lot,
Thomas
Ted Steen schrieb:
This happens because t
; in my project, i currently use hibernate 3.2.5 (and hibernate-search
> 3.0.0) together with tapestry 5.0.6 (and tapestry-hibernate module). The
> "normal" Hiberate works as excpeted, but the hibernate fulltext-search
> runs against an exception - i think because of wrong init
Hi,
in my project, i currently use hibernate 3.2.5 (and hibernate-search
3.0.0) together with tapestry 5.0.6 (and tapestry-hibernate module). The
"normal" Hiberate works as excpeted, but the hibernate fulltext-search
runs against an exception - i think because of wrong init of the
17 matches
Mail list logo
