[
https://issues.apache.org/jira/browse/OAK-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-801.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.11
Assignee: Jukka Zitting
Done in revision 1541229.
> Add Javadoc to JsonObject.create(JsopTokenizer)
> -----------------------------------------------
>
> Key: OAK-801
> URL: https://issues.apache.org/jira/browse/OAK-801
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Affects Versions: 0.7
> Reporter: Lukas Eder
> Assignee: Jukka Zitting
> Priority: Trivial
> Fix For: 0.11
>
>
> When browsing code, I was surprised to find a factory method
> JsonObject.create(JsopTokenizer), which operates on a tokenizer that is
> expected to be in some post-initialisation state. I.e. the following doesn't
> work:
> {code}
> JsonObject.create(new JsopTokenizer("{}"));
> {code}
> This does:
> {code}
> JsonObject.create(new JsopTokenizer("}"));
> {code}
> I understand that the goal of this method is to be used in larger JSON
> parsing contexts, where JsopTokenizer has already consumed a '{'. Since
> JsonObject is public and OSGi-exported, I think this method deserves at least
> some Javadoc.
> It might be better, of course, to provide a more predictable / reusable API.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
