You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Mark Slater (JIRA)" <ji...@apache.org> on 2006/03/21 07:45:04 UTC
[jira] Created: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
-----------------------------------------------------------------------------------------
Key: JCR-366
URL: http://issues.apache.org/jira/browse/JCR-366
Project: Jackrabbit
Type: Improvement
Reporter: Mark Slater
Priority: Minor
The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Created: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
Posted by Mark Slater <li...@humanesoftware.com>.
I have a patch for this, but keep getting InternalServerError when I
try to attach it to the issue. I'll try again sometime tomorrow.
Mark
On Mar 20, 2006, at 10:45 PM, Mark Slater (JIRA) wrote:
> Allow o.a.j.jca.JCARepositoryManager to load repository
> configuration from the classpath.
> ----------------------------------------------------------------------
> -------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Reporter: Mark Slater
> Priority: Minor
>
>
> The current implementation of o.a.j.jca.JCARepositoryManager is
> only able to load configuration files from the file system. It
> would be useful to allow the configuration to be loaded from the
> classpath also.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
[jira] Resolved: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Posted by "Edgar Poce (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-366?page=all ]
Edgar Poce resolved JCR-366:
----------------------------
Resolution: Fixed
thanks for the patch Mark
> Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
> -----------------------------------------------------------------------------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Components: jca
> Reporter: Mark Slater
> Assignee: Edgar Poce
> Priority: Minor
> Attachments: JCARepositoryManager.patch
>
> The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-366?page=all ]
Jukka Zitting updated JCR-366:
------------------------------
Fix Version: 1.1
Version: 1.0
1.0.1
> Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
> -----------------------------------------------------------------------------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Components: jca
> Versions: 1.0, 1.0.1
> Reporter: Mark Slater
> Assignee: Edgar Poce
> Priority: Minor
> Fix For: 1.1
> Attachments: JCARepositoryManager.patch
>
> The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Posted by "Edgar Poce (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-366?page=all ]
Edgar Poce reassigned JCR-366:
------------------------------
Assign To: Edgar Poce
> Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
> -----------------------------------------------------------------------------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Components: jca
> Reporter: Mark Slater
> Assignee: Edgar Poce
> Priority: Minor
> Attachments: JCARepositoryManager.patch
>
> The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Posted by "Roy T. Fielding (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-366?page=all ]
Roy T. Fielding updated JCR-366:
--------------------------------
Component: jca
> Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
> -----------------------------------------------------------------------------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Components: jca
> Reporter: Mark Slater
> Priority: Minor
> Attachments: JCARepositoryManager.patch
>
> The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-366) Allow o.a.j.jca.JCARepositoryManager to
load repository configuration from the classpath.
Posted by "Mark Slater (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-366?page=all ]
Mark Slater updated JCR-366:
----------------------------
Attachment: JCARepositoryManager.patch
This patch checks for the "classpath:" prefix in the configPath. If present, it attempts to load the class from the classpath and passes an InputStream to RepositoryConfig.create(). If the prefix is not present, the path is passed to RepositoryConfig.config() as is. I chose the prefix because it is the same used in the Spring Framework. Its a public static final variable (CLASSPATH_CONFIG_PREFIX), so if that's not a good choice for Jackrabbit, it can be easily changed.
The patch also adds a bit of parameter documentation.
> Allow o.a.j.jca.JCARepositoryManager to load repository configuration from the classpath.
> -----------------------------------------------------------------------------------------
>
> Key: JCR-366
> URL: http://issues.apache.org/jira/browse/JCR-366
> Project: Jackrabbit
> Type: Improvement
> Reporter: Mark Slater
> Priority: Minor
> Attachments: JCARepositoryManager.patch
>
> The current implementation of o.a.j.jca.JCARepositoryManager is only able to load configuration files from the file system. It would be useful to allow the configuration to be loaded from the classpath also.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira