Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.0
-
Fix Version/s: 5.0.0
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Fix Version/s | 5.0.0 [ 10931 ] |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All error is a technical error except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** file not found ** base directory not found * {{mget}}: ** base directory not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All error is a technical error except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found ** file not found * {{mget}}: ** base directory not found |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All error is a technical error except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found ** file not found * {{mget}}: ** base directory not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All error is a technical error except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found, ** file not found * {{mget}}: ** base directory not found |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All error is a technical error except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found, ** file not found * {{mget}}: ** base directory not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found, ** file not found * {{mget}}: ** base directory not found |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** base directory not found, ** file not found * {{mget}}: ** base directory not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found, * {{mget}}: ** filename missing in request |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found, * {{mget}}: ** filename missing in request |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{dir}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{dir}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{del}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
| Component/s | Operation 'checkFile' [ 10394 ] | |
| Component/s | Operation 'del' [ 10393 ] |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{del}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{del}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found, * {{mput}}: ** at least on attachment expected |
| Component/s | Operation 'mput' [ 10395 ] |
| Description |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{del}}, {{mget}}: ** filename missing in request, * {{get}}, {{getAsAttachment}}: ** filename missing in request, ** file not found, * {{mput}}: ** at least on attachment expected |
Currently, IO errors are returned as a fault.
We should distinguish between IO errors as technical errors or business errors. Technical errors should be returned as simple error, instead of business errors that should be returned as faults. All errors are technical errors except the following ones, per operation: * {{check}}, {{del}}, {{mget}}: ** filename missing in request, * {{get}}: ** filename missing in request, ** file not found, ** XML file expected, * {{getAsAttachment}}: ** filename missing in request, ** file not found, * {{mput}}: ** at least on attachment expected |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Reworked in branch petals-bc-filetransfer-5.0.x