Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.4
-
Fix Version/s: 2.4.1
-
Component/s: None
-
Security Level: Public
-
- Environment:
- Windows XP.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Minor [ 4 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Open [ 10002 ] |
| Description |
If we try to invoke a XSL transformation with invalid parameters and with the InOnly MEP, a fault is set on the exchange.
This is not allowed with this pattern. Besides, the faults are built manually. If it works correctly with Java clients, the faults should still be SOAP faults. |
If we try to invoke a XSL transformation with invalid parameters and with the InOnly MEP, a fault is set on the exchange.
This is not allowed with this pattern. {quote} Besides, the faults are built manually. If it works correctly with Java clients, the faults should still be SOAP faults. {quote} This second point needs to be discussed and will be the object of another report if it is confirmed. |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 2.4.1 [ 10154 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Summary | Invalid management of faults in the component | Invalid behavior with the InOnly MEP |