[
https://issues.apache.org/jira/browse/SLING-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated SLING-10625:
------------------------------
Description:
When a repoinit visitor catches an exception it wraps this exception into a
RuntimeException. In case the original exception is an
InvalidItemStateException, the retry mechanism introduced in SLING-10418 is not
able to retry.
This should be changed, instead of wrapping the Exception the exception should
just be thrown, the special handling of report should not be required at all.
Also a retry is not required.
was:
When a repoinit visitor catches an exception it wraps this exception into a
RuntimeException. In case the original exception is an
InvalidItemStateException, the retry mechanism introduced in SLING-10418 is not
able to retry.
This should be changed, instead of wrapping the Exception the exception should
just be thrown, the special handling of report should not be required at all.
> Repoinit Visitors should not throw RuntimeExceptions
> ----------------------------------------------------
>
> Key: SLING-10625
> URL: https://issues.apache.org/jira/browse/SLING-10625
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.36
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
> Fix For: Repoinit JCR 1.1.38
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When a repoinit visitor catches an exception it wraps this exception into a
> RuntimeException. In case the original exception is an
> InvalidItemStateException, the retry mechanism introduced in SLING-10418 is
> not able to retry.
> This should be changed, instead of wrapping the Exception the exception
> should just be thrown, the special handling of report should not be required
> at all. Also a retry is not required.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
