[
https://issues.apache.org/jira/browse/WICKET-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947648#comment-16947648
]
ASF subversion and git services commented on WICKET-6704:
---------------------------------------------------------
Commit 9e0201c0505e9c2c4369b8e14c1caa0be46e61a7 in wicket's branch
refs/heads/master from Martin Grigorov
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=9e0201c ]
WICKET-6704 JavaSerializer.serialize causes the JVM crash ! (#385)
* WICKET-6704 JavaSerializer.serialize causes the JVM crash !
Do not check instances of PropertyChangeSupport whether they are Serializable
because PropertyChangeSupport#writeObject() adds extra fields which confuse
CheckingObjectOutputStream
* WICKET-6704 Add more special types which use ObjectOutputStream.PutField in
their writeObject() method
(cherry picked from commit 4ff101fca5fac22dfab9dda4dcfe9075247ee46a)
> JavaSerializer.serialize causes the JVM crash !
> -----------------------------------------------
>
> Key: WICKET-6704
> URL: https://issues.apache.org/jira/browse/WICKET-6704
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 8.5.0
> Environment: Windows 7, but probably it's NOT OS dependant
> Reporter: Joe K
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Attachments: WicketObjects_stacktrace_1.jpg, jvm-crash_from_wicket.zip
>
>
> * when trying to serialize my custom object with a non-serializable field by
> JavaSerializer.serialize the JVM crashes instead of throwing the regular
> NotSerializableException !
> * when trying to serialize THE SAME object by java ObjectOutputStream then
> it's handled correctly and NotSerializableException is thrown
> * I'm attaching the very simple source code (Maven project), 1st test
> simulates the wicket issue (JVM crash) and 2nd test simulates the correct
> handling by java ObjectOutputStream
> * the attached example is just the simplification of very large project
> which is massively used by the users, so in fact it's critical for us
>
> * java: 1.8 (probably doesn't matter, tested on 1.8.0_162 and 1.8.0_221)
> * wicket: 8.5.0 (probably the problem is also in other versions)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
