Javassist
  1. Javassist
  2. JASSIST-97

Javassist doesn't serialize the handler along with the proxy

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 3.11.0.GA
    • Fix Version/s: 3.12.0.GA
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      When serializing a proxy, Javassist doesn't consider serializing the instance handler, but only the default handler.

      1. JASSIST-97.patch
        7 kB
        Mark Struberg
      2. JASSIST-97-test.diff
        10 kB
        Pete Muir

        Issue Links

          Activity

          Hide
          Shigeru Chiba
          added a comment -

          Great! The patch looks good. I will check the patch more carefully and apply it if it is OK.

          Show
          Shigeru Chiba
          added a comment - Great! The patch looks good. I will check the patch more carefully and apply it if it is OK.
          Hide
          Shigeru Chiba
          added a comment -

          I applied Mark's patch. Now it is available from SVN.

          Show
          Shigeru Chiba
          added a comment - I applied Mark's patch. Now it is available from SVN.
          Hide
          Andrew Dinn
          added a comment -

          See the dev forum for a proposed solution to this problem

          http://community.jboss.org/thread/149524

          Show
          Andrew Dinn
          added a comment - See the dev forum for a proposed solution to this problem http://community.jboss.org/thread/149524
          Hide
          Andrew Dinn
          added a comment -

          Fixed caching problems and provided new serialize/deserialize model using subclasses ProxyObjectOutputStream and ProxyObjectInputStream of, respectibely, ObjectOutputStream and ObjectInputStream. See javadoc in ProxyFactory for details.

          Added tests to check that old and new style proxy creation both work and that old and new style serialization also both work.

          Show
          Andrew Dinn
          added a comment - Fixed caching problems and provided new serialize/deserialize model using subclasses ProxyObjectOutputStream and ProxyObjectInputStream of, respectibely, ObjectOutputStream and ObjectInputStream. See javadoc in ProxyFactory for details. Added tests to check that old and new style proxy creation both work and that old and new style serialization also both work.
          Hide
          Steve Ebersole
          added a comment -

          Sort of unrelated (and I apologize for that), but Hibernate users are reporting issues with enhancing classes that have an attribute named 'handler' and thus a getter of getHandler() because it clashes with ProxyObject#getHandler(). They pointed to this issue as having possibly fixed that temporarily.

          Anyway, is this problem known and being worked on by renaming that method?

          Show
          Steve Ebersole
          added a comment - Sort of unrelated (and I apologize for that), but Hibernate users are reporting issues with enhancing classes that have an attribute named 'handler' and thus a getter of getHandler() because it clashes with ProxyObject#getHandler(). They pointed to this issue as having possibly fixed that temporarily. Anyway, is this problem known and being worked on by renaming that method?

            People

            • Assignee:
              Andrew Dinn
              Reporter:
              Pete Muir
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: