[
https://issues.apache.org/jira/browse/SLING-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Müller updated SLING-1576:
-------------------------------
Attachment: sling-1576.patch
I applied a patch to implement the proposed behavour. The listener service only
gets an INIT and a DESTROY event so far, but could be extended in the future.
That's the reason why the SlingRequestListener has a different signature than
the ServletRequestListener.
I would like to get some input before I commit, because it seems to be a wicket
topic, or should I rather interpret the silence on [1] and [2] as quiet
agreement ;-))?
[1] http://markmail.org/message/aovh7lll4w6uwepv
[2] http://markmail.org/message/wdymy2dttsdln7u2
> Provide a Sling request listener independent from a specific HTTP service
> -------------------------------------------------------------------------
>
> Key: SLING-1576
> URL: https://issues.apache.org/jira/browse/SLING-1576
> Project: Sling
> Issue Type: New Feature
> Components: API, Engine
> Affects Versions: Engine 2.0.6, API 2.0.8
> Reporter: Mike Müller
> Assignee: Mike Müller
> Priority: Minor
> Attachments: sling-1576.patch
>
>
> A listener should register as a service (SlingRequestListener) and get events
> during the processing of the request, similar to the ServletRequestListener.
> As discussed in [1] with this extension it would be possible to implement the
> separation of getting and validating the credentials as proposed by Felix on
> [2].
> [1] http://markmail.org/message/aovh7lll4w6uwepv
> [2] http://cwiki.apache.org/SLING/user-authentication.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
