On Nov 29, 2007 3:10 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...While it is probably useful in certain situations to have the session > available, I am not so sure, whether this should be documented and > become part of the API or whether we should just have it. ... For microsling the JCR Session is required in several places, and before this change it was acquired in an ugly way. If it is needed in Sling as well, we could either add a getJcrSession() method to SlingHttpServletRequest, or at least make the attribute name a constant to expose its use. >.... OTOH I am not > a fan of these hidden features, you know are there, but seem to be part > of an expected behaviour.... Agreed, so documenting the possible Request attributes might be the best way to solve this. -Bertrand
