[
https://issues.apache.org/jira/browse/CMIS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume resolved CMIS-127.
------------------------------------
Resolution: Fixed
r915409
Removed ContentManager, APPContentManager.
Added RepositoryManager, APPRepositoryService, etc.
For example to directly lookup an AtomPub repository, you now do:
Repository repo = new APPRepositoryService(URL,
null).getDefaultRepository();
Or you register it from some initialization code, then look it up from other
code:
RepositoryService repositoryService = new APPRepositoryService(URL, null);
RepositoryManager.getInstance().registerService(repositoryService);
// ...
Repository repo = RepositoryManager.getInstance(). getDefaultRepository();
When getting a Connection or a SPI from a Repository, you must now always pass
authentication parameters. The standard ways is:
Map<String, Serializable> params = new HashMap<String, Serializable>();
params.put(Repository.PARAM_USERNAME, username);
params.put(Repository.PARAM_PASSWORD, password);
Connection conn = repo.getConnection(params);
This will be improved later to allow other authentication schemes.
> Better way to register Repository instances and look them up
> ------------------------------------------------------------
>
> Key: CMIS-127
> URL: https://issues.apache.org/jira/browse/CMIS-127
> Project: Chemistry
> Issue Type: Improvement
> Components: chemistry-api
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
>
> We need a global way to register Repository instances in a JVM, and look them
> up when needed.
> To that effect, add a global RepositoryManager singleton that collects all
> registered repositories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
