[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-577) IllegalArgumentException when using @Proxy and trying to delete a loaded but proxied class

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-577?pag... ] Emmanuel Bernard commented on HSEARCH-577: ------------------------------------------ I've spend some time on the issue. The problem is that we enlist the required Method (getter in this case) from the actual physical class and not from the @Proxy.proxyClass. When an instance was initially lazy and subsequently loaded, the actually type is HibernateProxy_Javassistxyz and not the actual physical class (say Person). When trying to access the getter, the invoke operation fails. The solution is not trivial and would involve finding the referencing getter from the @Proxy.proxyClass class and use this one (exclusively or as a backup?). That's a lot of work though for a very edge case. I don't really have the necessary cycles to work on it but if someone from the community can step up and provide a solution, I will try and assist. The unit test is committed and available here http://github.com/emmanuelbernard/hibernate-search/commit/3d6b1243729b139... The work has to be done in AbstractDocumentBuilder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira