Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.4.2
-
Fix Version/s: 5.5.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | ||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|
|||||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Link | This issue blocks PETALSDISTRIB-133 [ PETALSDISTRIB-133 ] |
| Priority | Critical [ 2 ] |
| Link |
This issue blocks |
| Link |
This issue blocks |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Description |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: SOAP11FaultClientException can be safely removed from the CDK. |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: FaultException, DocumentException, SOAP11FaultServerException and SOAP11FaultClientException should be removed from the CDK. Note: these exception were used previously by components to build faults that were coherent with their WSDL: for that case, we should provide utils to create Fault from a Document or other XML in-memory representation of a fault. But that shouldn't be done using Java exceptions. |
| Description |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: FaultException, DocumentException, SOAP11FaultServerException and SOAP11FaultClientException should be removed from the CDK. Note: these exception were used previously by components to build faults that were coherent with their WSDL: for that case, we should provide utils to create Fault from a Document or other XML in-memory representation of a fault. But that shouldn't be done using Java exceptions. |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: FaultException, DocumentException, SOAP11FaultServerException and SOAP11FaultClientException should be removed from the CDK. Note: these exception were used previously by components to build faults that were coherent with their WSDL: for that case, we should provide utils to create Fault from a Document or other XML in-memory representation of a fault. But that shouldn't be done using Java exceptions (except maybe for the case of the POJO that seems to be relying on it... maybe we should move that "exception-based fault handling" logic to the pojo if we think current users of the component are exploiting them! (or provides an easy to use alternative)). |
| Link |
This issue depends on |
| Fix Version/s | 5.5.0 [ 10406 ] | |
| Priority | Critical [ 2 ] | Major [ 3 ] |
| Link |
This issue blocks |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: FaultException, DocumentException, SOAP11FaultServerException and SOAP11FaultClientException should be removed from the CDK. Note: these exception were used previously by components to build faults that were coherent with their WSDL: for that case, we should provide utils to create Fault from a Document or other XML in-memory representation of a fault. But that shouldn't be done using Java exceptions (except maybe for the case of the POJO that seems to be relying on it... maybe we should move that "exception-based fault handling" logic to the pojo if we think current users of the component are exploiting them! (or provides an easy to use alternative)). |
As per PETALSDISTRIB-133, technical errors should be kept as errors and not transformed to fault.
And Fault should NOT be SOAPFault, this is the role of the BC SOAP to do so, see: |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Link |
This issue blocks |
| Link |
This issue depends on |
| Link |
This issue blocks |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
The first commit left the various exceptions around FaultException but do not use them internally anymore.
They are there to keep the components using them working as they were, but they still need to be updated!