[
https://issues.apache.org/jira/browse/JCR-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644678#action_12644678
]
Thomas Mueller commented on JCR-1834:
-------------------------------------
It's great to have a implementation-independent way to open a repository!
This implementation can't do a few things. The following use cases are
unimportant for me, are they important for somebody else?:
- An application can not get a list of installed providers. Workaround: use
javax.imageio.spi.ServiceRegistry directly.
- An application can not specify what provider to use (using
RepositoryFactory): The repository factory calls connect on each provider, and
returns the repository of the first provider that doesn't return null.
Workaround: call the implementation directly.
- An application can not find out what properties need to be set. I don't know
of a workaround. It could be solved by adding
RepositoryFactory.getParameterInfo similar to java.sql.Driver.getPropertyInfo.
> Create RepositoryFactory implementation
> ---------------------------------------
>
> Key: JCR-1834
> URL: https://issues.apache.org/jira/browse/JCR-1834
> Project: Jackrabbit
> Issue Type: New Feature
> Components: JCR 2.0
> Reporter: Marcel Reutegger
> Priority: Minor
> Attachments: jackrabbit-api.patch, jackrabbit-core.patch,
> jackrabbit-jcr-rmi.patch
>
>
> JSR 283 specifies a RepositoryFactory to retrieve a repository instance based
> on a map of parameters. We should have the following implementations:
> - local repository with repository home and repository configuration
> parameters
> - repository obtained via JNDI
> - repository obtained via RMI
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
