[SLING-1183] Log RepositoryException on debug level if obtaining JCR session fails

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Engine 2.0.4
• Fix Version/s: Engine 2.1.0
• Component/s: Engine
• Assignee: Felix Meschberger
• Reporter: Honwai Wong
• Created: 11/Nov/09 16:41
• Updated: 30/Aug/10 16:48
• Resolved: 11/Nov/09 17:06

Description

If the SlingAuthenticator#authenticate method is unable to obtain a JCR session based on the given credentials, a RepositoryException is caught silently without further notice on the exact root cause. While this is an expected behavior, a more verbose logging would be helpful for debugging purposes. Though the handleImpersonation method already provides some pointers as to the initial cause, I'd prefer to have the full stacktrace of the RepositoryException at hand.

I suggest to log the full RepositoryException on DEBUG level.