Petals BC REST

Properly handles business faults from/to REST

Details

  • Description:
    Hide

    Following PETALSBCREST-1, we should now properly handle business faults in the REST BC.

    On provider side, now the HTTP code different from 20x are transformed into JBI errors. We should be able to generate fault on HTTP codes that have such a meaning.

    On consumer side, on fault, a HTTP code 500 is returned. We should be able to return different HTTP code according to the received fault.

    Show
    Following PETALSBCREST-1, we should now properly handle business faults in the REST BC. On provider side, now the HTTP code different from 20x are transformed into JBI errors. We should be able to generate fault on HTTP codes that have such a meaning. On consumer side, on fault, a HTTP code 500 is returned. We should be able to return different HTTP code according to the received fault.
  • Environment:
    -

Issue Links

Activity

Victor NOËL made changes - Wed, 15 Jul 2015 - 13:41:57 +0200
Field Original Value New Value
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Wed, 15 Jul 2015 - 13:42:23 +0200
Link This issue depends on PETALSBCREST-1 [ PETALSBCREST-1 ]
Victor NOËL made changes - Wed, 15 Jul 2015 - 13:48:02 +0200
Link This issue blocks PETALSDISTRIB-133 [ PETALSDISTRIB-133 ]
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 10:46:04 +0100
Priority Major [ 3 ]
Description Following PETALSBCREST-1, we should now properly handle business faults in the REST BC.

For now the HTTP errors are Errors, business Faults should be recognised as such, it's not clear how.
Maybe there is some kind of norm to recognise a business fault from a normal answer in REST.
Following PETALSBCREST-1, we should now properly handle business faults in the REST BC.

On provider side, now the HTTP code different from 20x are transformed into JBI errors. We should be able to generate fault on HTTP codes that have such a meaning.

On consumer side, on fault, a HTTP code 500 is returned. We should be able to return different HTTP code according to the received fault.
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 10:52:35 +0100
Status New [ 10000 ] Open [ 10002 ]
Assignee Victor NOËL [ vnoel ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 11:55:40 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 11:56:41 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.0.2 [ 10696 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 11:57:01 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 29 Dec 2016 - 17:32:58 +0100
Link This issue blocks PETALSBCREST-8 [ PETALSBCREST-8 ]
Christophe DENEUX made changes - Wed, 25 Jan 2017 - 17:17:43 +0100
Link This issue depends on PETALSBCREST-29 [ PETALSBCREST-29 ]
Christophe DENEUX made changes - Tue, 14 Feb 2017 - 17:57:26 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 14 Feb 2017 - 18:01:26 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Tue, 14 Feb 2017 - 18:01:58 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Component/s Consumer mode [ 10403 ]
Component/s Provider mode [ 10404 ]
Christophe DENEUX made changes - Thu, 4 Jan 2018 - 11:16:37 +0100
Fix Version/s 1.1.1-BC [ 10768 ]
Christophe DENEUX made changes - Thu, 15 Feb 2018 - 14:48:49 +0100
Fix Version/s 1.1.2-BC [ 10821 ]
Fix Version/s 1.1.1-BC [ 10768 ]
Christophe DENEUX made changes - Thu, 26 Jul 2018 - 16:45:54 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 26 Jul 2018 - 16:46:10 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Wed, 15 Jul 2015 - 13:41:51 +0200
    Updated:
    Thu, 26 Jul 2018 - 16:47:00 +0200
    Resolved:
    Thu, 26 Jul 2018 - 16:46:10 +0200