You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/02/06 08:09:59 UTC

[jira] Commented: (WICKET-2077) SerializationChecker issue

    [ https://issues.apache.org/jira/browse/WICKET-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671024#action_12671024 ] 

Igor Vaynberg commented on WICKET-2077:
---------------------------------------

how can one of the methods not be available?

> 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.