[jira] Updated: (OWB-399) Proxy objects could not be correctly deserialized by using javassist 3.11. we need to update to 3.12

["Mark Struberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg updated OWB-399:
------------------------------

        Fix Version/s: 1.0.0-CR1
                           (was: 1.0.0-CR2)
           Issue Type: Bug  (was: Improvement)
             Assignee: Mark Struberg  (was: Gurkan Erdogdu)
    Affects Version/s: M4
                           (was: 1.0.0-CR1)
             Priority: Blocker  (was: Major)

Hi ying!

That's exactly the reason why I fixed javassist ;) Itmt my patch got applied and Andrew Dinn and David Allen also fixed a lot other parts. I'm currently working on getting this new version of javassist to maven.central so we can use it for releasing CR1.

> Proxy objects could not be correctly deserialized by using javassist 3.11. we need to update to 3.12
> ----------------------------------------------------------------------------------------------------
>
>                 Key: OWB-399
>                 URL: https://issues.apache.org/jira/browse/OWB-399
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: M4
>            Reporter: YING WANG
>            Assignee: Mark Struberg
>            Priority: Blocker
>             Fix For: 1.0.0-CR1
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> While I am investigating owb failover / passivation support , I encountered an issue that de-serialized proxy object could not delegate calls to bean instance object methods. The handler field held by the proxy object ( such as NormalScopeBeanInterceptorHandler we used for normal scope ) is replaced with javassist default handler. 
> Sandbox tests show hat if I upgrade to javassist 3.12 and use ProxyObjectInputStream/ProxyObjectOutputStream, the handler in de-serialized proxy object get restored correctly.
> But 3.12 is not in jboss repository yet, anyone know if there is a way  to push them update their javasssist repository? or create our own snapshot repository temporarily? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.