[metadata transformation] better error handling in XSLT transformation #253

Closed
claudio.atzori wants to merge 3 commits from transformation_wf into beta

This PR addresses #252 by improving the error handling in the XSLT-based transformation workflow, separating the XSLT creation errors from the XSLT application, and letting the 1st propagate. Furthermore, every error is gathered in the AggregationReport object and reported back to the MSRO.

This PR addresses #252 by improving the error handling in the XSLT-based transformation workflow, separating the XSLT creation errors from the XSLT application, and letting the 1st propagate. Furthermore, every error is gathered in the `AggregationReport` object and reported back to the MSRO.
claudio.atzori added the
enhancement
bug
labels 2022-09-28 14:18:50 +02:00
claudio.atzori self-assigned this 2022-09-28 14:18:51 +02:00
claudio.atzori added 1 commit 2022-09-28 14:18:56 +02:00
claudio.atzori added 1 commit 2022-09-28 14:19:08 +02:00
claudio.atzori requested review from sandro.labruzzo 2022-09-28 14:19:18 +02:00
claudio.atzori requested review from alessia.bardi 2022-09-28 14:19:19 +02:00

Let's test how it goes, to make sure

  • we do not get any unexpected null pointers for the counters in the report
  • the transformation fails at the first record in case the mapping is not well formed
Let's test how it goes, to make sure - we do not get any unexpected null pointers for the counters in the report - the transformation fails at the first record in case the mapping is not well formed
claudio.atzori added 1 commit 2022-09-29 11:05:54 +02:00
claudio.atzori closed this pull request 2024-06-26 10:17:14 +02:00

Pull request closed

Sign in to join this conversation.
No description provided.