[
https://issues.apache.org/jira/browse/WICKET-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671543#action_12671543
]
Alex commented on WICKET-2077:
------------------------------
Some embedded JVMs we work with do not implement LOOKUP.
This leaves us without any workarounds short of modifying the source.
There is no easy way to turn the use of SerializationChecker off.
By the way what was the intent of the SerializationChecker.isAvailable() any
way if not to check whether it works on the target JVM?
> 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
>
> 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.
