[
https://issues.apache.org/jira/browse/WICKET-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2077.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC3
1.3.6
Assignee: Igor Vaynberg
i changed the code so it does not throw a runtime exception - which is what
cause your embedded jvm to not load the class. instead it now logs a warning.
there is an easy way to turn it off, simply install your own
IObjectStreamFactory that does not use the checker. the simplest variant can be
class myfactory extends DefaultObjectStreamFactory {
public ObjectOutputStream newObjectOutputStream(final OutputStream out)
throws IOException
{return new ObjectOutputStream(out);}
}
> SerializationChecker issue
> --------------------------
>
> Key: WICKET-2077
> URL: https://issues.apache.org/jira/browse/WICKET-2077
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Reporter: Alex
> Assignee: Igor Vaynberg
> Fix For: 1.3.6, 1.4-RC3
>
>
> When the static initialization of the SerializationChecker class fails (one
> of the methods is not available) it throws a runtime exception which marks
> the SerializationChecker class as unavailable in the JVM. Using the
> SerializationChecker class after that to check for SerializationChecker
> .isAvailable is pointless because it throws the ClassNotFound exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
