[
https://issues.apache.org/jira/browse/COMMONSRDF-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237668#comment-16237668
]
ASF GitHub Bot commented on COMMONSRDF-49:
------------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/commons-rdf/pull/43
Well, it's hard for me to say, because I'm trying to predict the
architecture of a system I am only beginning to design. :(
@afs, @sebbASF, how about I break out a separate type for serializable
config and a builder for it and we take that forward? It might be enough and if
it isn't we can revisit the question then. I could leave `AbstractRDFParser`
as-is, although I'd rather alter it, both for the reasons @kinow gave in Jira
and if I break out a config-builder to indicate the preferred usage.
> Make AbstractRDFParser serializable
> -----------------------------------
>
> Key: COMMONSRDF-49
> URL: https://issues.apache.org/jira/browse/COMMONSRDF-49
> Project: Apache Commons RDF
> Issue Type: New Feature
> Components: simple
> Affects Versions: 0.3.0
> Reporter: Stian Soiland-Reyes
> Assignee: Andy Seaborne
> Priority: Major
> Labels: parser
> Fix For: 0.6.0
>
>
> Raised by [~p_ansell] in [pull request
> 25|(https://github.com/apache/incubator-commonsrdf/pull/25#discussion_r85436754]
> {quote}
> The use of optional here as a field type makes it impossible to serialise.
> Need to have the raw values stored in fields if you want to support
> serialisation in the future, which should otherwise be possible.
> {quote}
> The suggestion is to avoid {{Optional}} in the private fields of
> {{AbstractRDFParser}} so it can be serialized - it can still be {{Optional}}
> in the accessor methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
