You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Alex (JIRA)" <ji...@apache.org> on 2009/02/04 21:59:59 UTC
[jira] Created: (WICKET-2077) SerializationChecker issue
SerializationChecker issue
--------------------------
Key: WICKET-2077
URL: https://issues.apache.org/jira/browse/WICKET-2077
Project: Wicket
Issue Type: Bug
Components: wicket
Reporter: Alex
Fix For: 1.3.5
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.
[jira] Commented: (WICKET-2077) SerializationChecker issue
Posted by "Alex (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WICKET-2077) SerializationChecker issue
Posted by "Alex (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex updated WICKET-2077:
-------------------------
Fix Version/s: (was: 1.3.5)
Affects Version/s: 1.3.5
> 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.
[jira] Resolved: (WICKET-2077) SerializationChecker issue
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (WICKET-2077) SerializationChecker issue
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ 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.