On 5 Oct 2007, at 15:56, Felix Meschberger wrote:
What do you think of moving the o.a.s.content.ContentManager interface
to the Sling API and provide it through the ComponentRequest
instead of
having to access a request attribute:
public interface ComponentRequest extends HttpServletRequest {
....
public ContentManager getContentManager();
....
}
What do you think ? If feedback is positive, I would also include this
in the Sling API proposal (SLING-28).
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
-1
--
Torgeir Veimo
[EMAIL PROTECTED]
