[
https://issues.apache.org/jira/browse/SLING-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572435#action_12572435
]
Bertrand Delacretaz commented on SLING-268:
-------------------------------------------
> Note, that IMHO this ujax info stuff is not the right way to go for providing
> system information stuff.
> Rather we should strive for supporting JMX.
The current use case is to provide this information to javascript clients, so I
think an HTTP/json interface is more useful than JMX - although the former
could be a proxy on the latter.
> Dissolve launchpad/launchpad-servlets project
> ---------------------------------------------
>
> Key: SLING-268
> URL: https://issues.apache.org/jira/browse/SLING-268
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Felix Meschberger
> Fix For: 2.0.0
>
>
> The launchpad/launchpad-servlets project derives from the migration of µsling
> into Sling and has undergone some changes recently. To better separate the
> tasks involved with the servlets and to leverage the recent addition of more
> sophisticated servlet regitration, the launchpad/launchpad-servlets projects
> should be dissolved:
> (1) Default Servlets
> The Servlets and renderers in the o.a.s.launchpad.renderers package are moved
> to a new module sling/servlets-default and registered by themselves as
> sling/servlet/default for their respective request extensions supported.
> (2) UjaxPostServlet
> The classes in o.a.s.ujax are moved to a new sling/ujax module
> (3) UjaxInfoServlet
> The UjaxInfoServlet is also moved to the new sling/ujax module. In addition
> this servlet must be modified to not responde to /ujax:... but to /ujax.*
> where the extension selects the format of information presentation and the
> first selector defines the information presented. So the current
> "/ujax:sessionInfo.json" request would turn in "/ujax.sessionInfo.json" and
> can also be requested as "/ujax.sessionInfo.html" or "/ujax.sessionInfo.txt".
> (4) LaunchpadDefaultServlet
> Dropped because it is not needed any more.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
