Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.3.5
-
Fix Version/s: 4.4.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Minor [ 4 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
When a request is made from the exterior to our SOAP BC and there is an error in the processing, we should have meaningful messages.
Currently sometimes the content is incorrect, or meaningless. Also, when accessing the WSDL, (with ...serviceName?wsdl), if there is errors, they should be properly reported using the HTTP codes. |
When a request is made from the exterior to our SOAP BC (hence, for a Consumes) and there is an error in the processing, we should have meaningful messages.
Currently sometimes the content is incorrect, or meaningless. There should be clear errors for: - No JBI provider available - Error in the JBI exchange returned from the JBI provider Also, when accessing the WSDL, (with ...serviceName?wsdl), if there is errors, they should be properly reported using the HTTP codes and the stacktrace. |
| Link |
This issue blocks |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 4.4.0 [ 10405 ] | |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
To be clearer, can you add in the description which error cases are covered by this issue, as you started to do with errors on getting WSDL