You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/06/11 15:50:42 UTC
[jira] [Commented] (SLING-2508) Repository.xml should be made
available in Configuration Status
[ https://issues.apache.org/jira/browse/SLING-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292804#comment-13292804 ]
Felix Meschberger commented on SLING-2508:
------------------------------------------
Thanks for providing the patch.
I don't think this belongs to the Web Console core. I would rather see it as a ConfigurationPrinter service in the jackrabbit-server project.
Plus: I suggest to align access to the actual files with how the jackrabbit-server bundle actually accesses the files itself. And then I would think all configuration files (workspace.xml, search.xml, more ?) should be included.
> Repository.xml should be made available in Configuration Status
> ---------------------------------------------------------------
>
> Key: SLING-2508
> URL: https://issues.apache.org/jira/browse/SLING-2508
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Environment: All
> Reporter: Vishwa Sourabh Sahay
> Labels: patch
> Attachments: RepositoryDetailsPrinter.java.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Currently, the Repository details are available through JMX and Repository CRX tab in Configuration Status in Apache Felix console. While it contains some information, a few other pieces of information are missing. For instance, information such as LoginModule, DataStore configuration, TarPM settings are not available in JMX dump.There could be other settings too depending upon configuration in Repository and workspace xmls.
> Moreover, while performing diagnosis on particular system, it is always useful for developers/tech support team to have a look at these configuration(s) file to ascertain the settings on these systems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira