Petals SE XSLT

The SE should respect the InOut MEP

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: 2.3.2
Fix Version/s: 2.4
Component/s: None
Security Level: Public

Description:
Hide
The XSLT SE has two operations, working in InOut.
When something goes wrong (invalid operation, transformation failure), the SE sets an error on the exchange, instead of setting a fault.
This is not respectful of the InOut MEP.

Instead of setting an error, it should set a fault:

<?xml version="1.0" encoding="UTF-8"?> <xsltFault xmlns="the name space of the invoked operation"> <message>An error message</message> <details>A stack trace (optional)</details> </xsltFault>

If a problem occurs while setting the fault, then an error will be set.
Show
The XSLT SE has two operations, working in InOut. When something goes wrong (invalid operation, transformation failure), the SE sets an error on the exchange, instead of setting a fault. This is not respectful of the InOut MEP. Instead of setting an error, it should set a fault:

<?xml version="1.0" encoding="UTF-8"?> <xsltFault xmlns="the name space of the invoked operation"> <message>An error message</message> <details>A stack trace (optional)</details> </xsltFault>

If a problem occurs while setting the fault, then an error will be set.

Environment:

All.

Issue Links

Depends

This issue blocks:
~~PETALSSEXSLT-12~~ Properties of the incoming message should be passed to the XSL stylesheet as parameter

Activity

Descending order - Click to sort in ascending order

Hide

Permalink

Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 15:38:16 +0200 - edited

Commit # 15791
Commit # 15792

Show

Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 15:38:16 +0200 - edited Commit # 15791 Commit # 15792

People

Assignee:

Vincent Zurczak

Reporter:

Vincent Zurczak
Watchers:

0

Dates

Created:

Fri, 17 Sep 2010 - 15:16:27 +0200

Updated:

Fri, 17 Sep 2010 - 15:52:07 +0200

Resolved:

Fri, 17 Sep 2010 - 15:38:16 +0200