[
https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090145#comment-13090145
]
Thomas Mueller commented on JCR-3058:
-------------------------------------
The tool doesn't try to detect broken properties currently, who and why would
you want to detect them?
> I'm looking at a bundle that has >35 properties, how can I know what is going
> on?
I used it to manually read the data. I already knew the bundle was broken,
because loading the bundle failed, so I knew roughly what the problem was
(couldn't parse a timestamp because the year was out of range), but I needed to
see the actual data.
For what I used the tool (to easily analyze broken bundles), it works well, but
I wonder if adding more complexity is really necessary - I don't need more
features currently.
But if have a use case then that's different of course.
> BundleDumper to analyze broken bundles
> --------------------------------------
>
> Key: JCR-3058
> URL: https://issues.apache.org/jira/browse/JCR-3058
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to
> analyze broken bundles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
