You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/08/29 13:52:00 UTC

[jira] [Closed] (SLING-11364) Allow dedicated handling of networking issues

     [ https://issues.apache.org/jira/browse/SLING-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Hoh closed SLING-11364.
-----------------------------

> Allow dedicated handling of networking issues
> ---------------------------------------------
>
>                 Key: SLING-11364
>                 URL: https://issues.apache.org/jira/browse/SLING-11364
>             Project: Sling
>          Issue Type: Improvement
>          Components: Apache Sling Testing Clients
>    Affects Versions: Apache Sling Testing Clients 3.0.12
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: Apache Sling Testing Clients 3.0.14
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Right now the {{ClientException}} is the only exception which is used to report unexpected situations, including:
> * networking errors (e.g. timeouts)
> * unexpected statuscodes
> * or otherwise unexpected results.
> This makes is hard at the level of a test driver to easily split between infrastructure errors and actual test failures, because it always needs a lock into the logs of the test execution to distinguish these.
> To make such a change backwards-compatible, new Exceptions should be introduced which inherit from the existing {{ClientException}}. This does not require any changes to signatures, but allow the test-driver to clearly distinguish these different types of errors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)