You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2010/07/28 23:52:16 UTC

[jira] Commented: (SLING-1419) Remove dependency to JCR

    [ https://issues.apache.org/jira/browse/SLING-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893387#action_12893387 ] 

Justin Edelson commented on SLING-1419:
---------------------------------------

It seems like this issue should be retitled as "make JCR dependency optional" as we can't really remove the dependency completely.

assuming this is agreeable, this patch should do it: http://codereview.appspot.com/1884045

> Remove dependency to JCR
> ------------------------
>
>                 Key: SLING-1419
>                 URL: https://issues.apache.org/jira/browse/SLING-1419
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Auth 1.0.0
>            Reporter: Carsten Ziegeler
>             Fix For: Commons Auth 1.0.0
>
>
> The commons auth module as independent functionality wrt to JCR therefore we should make it work without JCR
> With SLING-1262 implemented, we can use the ResourceResolverFactory to login instead of going through the SlingRepository.
> In addition we should:
> - drop the setter and getter methods for credentials in the AuthenticationInfo - we keep the constant though
> - drop the setter and getter method for the workspace in the AuthenticationInfo - we keep the constant
> We make the import to the jcr packages optional as these are required for compatibility support of the old engine packages. If someone wants to use this support he'll need the jcr api anyway. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.