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

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2017/12/30 21:22:03 UTC

[jira] [Updated] (WICKET-6504) Using a serializable model for FileSystemResource's path

     [ https://issues.apache.org/jira/browse/WICKET-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov updated WICKET-6504:
------------------------------------
    Summary: Using a serializable model for FileSystemResource's path  (was: Using a serializable model for FileSystemResource)

> Using a serializable model for FileSystemResource's path
> --------------------------------------------------------
>
>                 Key: WICKET-6504
>                 URL: https://issues.apache.org/jira/browse/WICKET-6504
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 7.8.0
>            Reporter: Claudia Hirt
>            Assignee: Martin Grigorov
>            Priority: Minor
>
> FileSystemResource takes a java.nio.file.Path to load the resource. 
> This leads to java.io.NotSerializableException: sun.nio.fs.WindowsPath in my case. I know this is a problem of JavaSerializer and I already found the solution to use something like Kryo Serializer instead.
> But wouldn't it be better to have the possibility to use a Model for the path anyway?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)