[
https://issues.apache.org/jira/browse/SLING-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957377#comment-13957377
]
Carsten Ziegeler commented on SLING-3485:
-----------------------------------------
I think we should not export them in any way from the servlets get bundle.
Therefore if we make them publically available, another bundle would be the way
to go.
commons.json sounds like a good place, however the problematic part here is
that the bundles in commons are intended to be used outside of Sling and the
above classes use the Resource API. But maybe we can make an exception here as
it doesn't make too much sense to create yet another bundle for just those
classes.
if we add these to some public package, maybe we should look at the API again
and see if it needs cleanup
> 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)
