Provide access to server exception details

Description

The wfs-ng module drops WFS exception responses for Transaction requests and instead an empty IOException is thrown (TransactionResponseImpl.java:105, see https://github.com/geotools/geotools/blob/cfe895c1fe84c65904d1aa383496ed2aff7afa42/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/v1_x/TransactionResponseImpl.java#L105).

A better solutions is already implemented for the GetFeature case (AbstractGetFeatureResponseParserFactory#createResponse, see https://github.com/geotools/geotools/blob/cfe895c1fe84c65904d1aa383496ed2aff7afa42/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/parsers/AbstractGetFeatureResponseParserFactory.java#L108).

This solution should also be applied to the Transaction case.

One further issue:
AbstractGetFeatureResponseParserFactory.parseException(...) creates an ExceptionReportType having a list of code+message pairs. This information is converted into a plain WFSException retaining a concatenated string field only.
Suggestion: Extend WFSException to keep this information separately to be easier accessible for consumers.

Environment

None

Assignee

Unassigned

Reporter

Andreas W

Triage

None

Components

Fix versions

Affects versions

Priority

Medium
Configure