[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4649) HibernatePersistenceProvider proxies already proxied instances leading to exceptions in Hibernate Search

[Emmanuel Bernard (JIRA)]

     [ https://jira.jboss.org/browse/JBSEAM-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated JBSEAM-4649:
-------------------------------------

     Summary: HibernatePersistenceProvider proxies already proxied instances leading to exceptions in Hibernate Search  (was: HibernatePersistenceProvider has issues with Hibernate Search 3.2.0)
    Assignee: Emmanuel Bernard  (was: Marek Novotny)


> HibernatePersistenceProvider proxies already proxied instances leading to exceptions in Hibernate Search
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4649
>                 URL: https://jira.jboss.org/browse/JBSEAM-4649
>             Project: Seam
>          Issue Type: Bug
>          Components: Core, Search
>    Affects Versions: 2.2.1.CR1, 2.2.1.CR2
>         Environment: JBoss AS 6.0.0.M2
> Hibernate 3.5.1
> Hibernate Search 3.2.0
> Seam 2.2.1.CR1
>            Reporter: Tom Fank
>            Assignee: Emmanuel Bernard
>         Attachments: HibernatePersistenceProvider.patch
>
>
> The new proxied persistence provider (introduced in Seam 2.2.1.CR1) needs some rework in order to be compatible with the current release candidate of Hibernate Search...
> 1)
> When org.jboss.seam.persistence.HibernatePersistenceProvider is trying to find out if HSearch is available it expects org.hibernate.search.Version to have some static VERSION field, but current release does not provide it.
> 2)
> The org.jboss.seam.persistence.HibernateSessionInvocationHandler does not seem to respect the org.hibernate.event.EventSource interface of the delegated Hibernate session. But the (legacy) implementation of FullTextSession still relies on it, so invocations of methods like 'getActionQueue()' need to be handled correctly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira