You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/11 18:04:55 UTC

[jira] Resolved: (JCR-2460) Rename GenericRepositoryFactory to JndiRepositoryFactory

     [ https://issues.apache.org/jira/browse/JCR-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-2460.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Done in revision 897935.

> Rename GenericRepositoryFactory to JndiRepositoryFactory
> --------------------------------------------------------
>
>                 Key: JCR-2460
>                 URL: https://issues.apache.org/jira/browse/JCR-2460
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-commons
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The GenericRepositoryFactory class introduced in JCR-2360 has since been refactored so that most of its functionality is now distributed among the more implementation-specific RepositoryFactory classes. Now the GenericRepositoryFactory only contains support for looking the repository up in JNDI, so it would be better to rename the class to JndiRepositoryFactory.
> The only troublesome part of the rename is the GenericRepositoryFactory.URI constant that was for a while documented on our wiki as a part of the canonical code snippet for accessing a remote repository based on the repository URI. The latest recommendation is to use the JcrUtils.getRepository(String uri) method so the constant is no longer needed in client code, but for backwards compatibility with earlier Jackrabbit 2.0 betas it may be good to keep the deprecated constant for at least the next beta release.

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