You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2013/12/06 17:01:37 UTC

[jira] [Commented] (CLEREZZA-850) SolutionMapping implementation is not serializable

    [ https://issues.apache.org/jira/browse/CLEREZZA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841376#comment-13841376 ] 

Reto Bachmann-Gmür commented on CLEREZZA-850:
---------------------------------------------

VETOed Change, see Mailing List. The Problematic part is Resources and thus becoming seriualizable.

> SolutionMapping implementation is not serializable
> --------------------------------------------------
>
>                 Key: CLEREZZA-850
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-850
>             Project: Clerezza
>          Issue Type: Bug
>          Components: rdf.core
>            Reporter: Minto van der Sluis
>            Assignee: Minto van der Sluis
>            Priority: Critical
>
> The SolutionMapping implementation HashMapSolutionMapping itself is serializable since the underlying HashMap is serializable. However the key (Variable) and value (Resource) are not serializable. So as a whole SolutionMapping can not be serialized.
> Serialization is needed to create a SolutionMapping based model in an Apache Wicket based project. Now there are 2 posiblities to fix this:
> 1) Wrap SolutionMapping in a serialized equivalent
> 2) Make the necessary Clerezza parts serializable
> If there aren't any objections. I prefer option 2. Making the right components serializable.



--
This message was sent by Atlassian JIRA
(v6.1#6144)