[
https://issues.apache.org/jira/browse/SLING-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-3485:
----------------------------
Attachment: SLING-3485.diff
Sorry for taking so long to follow up with this. I marked the Sling API as
optional and put the classes in the package
`org.apache.sling.commons.json.sling`. I also marked the JCR API import as
optional, since that's not really required either for the core functionality of
the JSON Serialization.
That all make sense? Should I go ahead an commit it? Updated patch attached.
> Expose JSON Servlet Helpers
> ---------------------------
>
> Key: SLING-3485
> URL: https://issues.apache.org/jira/browse/SLING-3485
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Get 2.1.8
> Reporter: Dan Klco
> Priority: Minor
> Labels: easyfix, patch
> Attachments: SLING-3485.diff
>
>
> Right now the following classes which are used for the JsonRendererServletare
> not exported from the bundle. From a developer's perspective, I may want to
> use these classes to remix the Resource -> JSON functionality without having
> to re-write the code.
> -
> https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/JsonObjectCreator.java
> -
> https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/ResourceTraversor.java
> I propose we refactor these classes to be in the package
> org.apache.sling.servlets.get.helpers which will expose them to the OSGi
> Container.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
