[
https://issues.apache.org/jira/browse/FELIX-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506873#comment-15506873
]
David Bosschaert commented on FELIX-5332:
-----------------------------------------
Hi [~dleangen], this is quite a substantial amount of functionality! :)
What I think might be a good idea is to isolate it out into its own module.
Alongside converter and serializer, maybe something called
'org.apache.felix.schematizer'. I think for the API we should probably use API
in the org.apache.felix namespace for the moment. Then we can maybe add a
withContext(Object obj) to the Serializer interface (or maybe to the
Serializing/Deserializing ones). This could be a generic mechanism to provide
implementation-specific context to the serializer, which could be the Schema in
this case.
Reason for such an approach is that the converter is currently super-light. It
would be nice to keep it light IMHO. Having it as a separate module means that
only those who need this advanced feature get the complexity.
WDYT?
> Serializer
> ----------
>
> Key: FELIX-5332
> URL: https://issues.apache.org/jira/browse/FELIX-5332
> Project: Felix
> Issue Type: New Feature
> Components: Converter
> Reporter: David Leangen
> Assignee: David Bosschaert
> Attachments: patch.diff
>
>
> Test case and a bit of code to show how a Serializer could work.
> To work as a Serializer, the type information needs to be embedded into the
> output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
