[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2567) Javassist proxies aren't being correctly serialized
[ http://jira.jboss.com/jira/browse/JBSEAM-2567?page=comments#action_12399553 ]
Davide Orlandi commented on JBSEAM-2567:
----------------------------------------
I noticed that remoting references to javassist proxies causes the same problem as
described in #JBSEAM-1305 ("member" tag opened but not closed for property
"handler").
Tested with Seam 2.0.1 and hibernate 3.2.5.
Indeed it can be fixed with a workaround similar for the one for cglib:
if (cls.getName().contains("_$$_javassist_"))
cls=cls.getSuperclass();
at line 200 of BeanWrapper.
Javassist proxies aren't being correctly serialized
---------------------------------------------------
Key: JBSEAM-2567
URL: http://jira.jboss.com/jira/browse/JBSEAM-2567
Project: JBoss Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.0.1.GA
Reporter: Shane Bryzak
Assigned To: Shane Bryzak
Fix For: 2.0.2.GA
Stuff like this is appearing in the response packets for remoting quests:
<ref id="52"><bean
type="org.domain.remote.entity.Application_$$_javassist_67"><member
name="applicationName">
This is definitely bad, and probably needs a similar workaround to what was done for
cglib in BeanWrapper.serialize()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira