You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Minto van der Sluis (JIRA)" <ji...@apache.org> on 2014/05/22 14:00:06 UTC

[jira] [Comment Edited] (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=14005835#comment-14005835 ] 

Minto van der Sluis edited comment on CLEREZZA-850 at 5/22/14 11:59 AM:
------------------------------------------------------------------------

Added serialization. This time not on Resource itself (due to valid objections by Reto) but on the various implementations of Resource (except for BNode)


was (Author: misl):
Added serialization. This time not on Resource itself (due to valid objection by Reto) but on the various implementations of Resource (expect for BNode)

> 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.2#6252)