[
https://issues.apache.org/jira/browse/FELIX-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848627#comment-15848627
]
David Leangen commented on FELIX-5508:
--------------------------------------
I am not yet familiar enough with how Felix is organized to directly comment,
but I do have a few things on my mind.
I find that the "danger" of this type of (parser/writer) utility is that it can
quickly turn into a full-fledged parser project. It is a slippery slope. ("Just
need this one more little feature...") That is why there quickly become
numerous similar "utilities" throughout the code base. Reminds me of [this
funny comic|https://xkcd.com/927/]. Not sure how to do it, but there should be
some kind of strict oversight regarding what this "utility" does.
I would propose, for starters:
* NOT user-friendly for use as an all-purpose library
* NOT configurable (or perhaps only "minimally" configurable, but again,
slippery slope)
Should it be only for internal Felix use as a library that gets embedded in the
using bundle (and thus repeated in the live system)?
Should it be more DRY, and maybe accessible to other projects, for instance as
an OSGi service?
I am leaning towards an internal Felix library, in order to try to avoid all
the scope creep. Would putting it in utils solve these issues, do you think?
(Sorry if any of these comments are silly. I'm just trying to find my legs
here. :-)
> Multiple JSON Serializers
> -------------------------
>
> Key: FELIX-5508
> URL: https://issues.apache.org/jira/browse/FELIX-5508
> Project: Felix
> Issue Type: Improvement
> Components: Converter
> Reporter: David Leangen
>
> There appears to be multiple json serializers in the code base (serializer,
> schematizer, and even more recently webconsole).
> Would it be worthwhile to consider consolidating them somehow, to avoid
> duplicate work?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
