Petals SE JSR181

Properly handles business faults from/to JSR181

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 1.4.3
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Following PETALSSEJSR-28, business faults should also be handled correctly.

    Axis (used to do the JSR181 integration) throws AxisFault for business faults (exceptions thrown by WebService annotated methods) and we should try to detect them and transform them into JBI faults.

    We noted in the previous issue:

    The problem is maybe that using Axis, we HAVE to go through the SOAP format and through all the remote layers even though we stay in-memory... I'm wondering if this is the right tool for this job... this must be investigated.

    Show
    Following PETALSSEJSR-28, business faults should also be handled correctly. Axis (used to do the JSR181 integration) throws AxisFault for business faults (exceptions thrown by WebService annotated methods) and we should try to detect them and transform them into JBI faults. We noted in the previous issue:
    The problem is maybe that using Axis, we HAVE to go through the SOAP format and through all the remote layers even though we stay in-memory... I'm wondering if this is the right tool for this job... this must be investigated.
  • Environment:
    -

Issue Links

Activity

Victor NOËL made changes - Wed, 15 Jul 2015 - 13:46:26 +0200
Field Original Value New Value
Assignee Vincent Zurczak [ vzurczak ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Wed, 15 Jul 2015 - 13:46:47 +0200
Link This issue depends on PETALSSEJSR-28 [ PETALSSEJSR-28 ]
Victor NOËL made changes - Wed, 15 Jul 2015 - 13:48:14 +0200
Link This issue blocks PETALSDISTRIB-133 [ PETALSDISTRIB-133 ]

People

Dates

  • Created:
    Wed, 15 Jul 2015 - 13:46:19 +0200
    Updated:
    Wed, 15 Jul 2015 - 13:48:14 +0200