Petals BC SOAP

A module configured at the SU level is invoked on all services of the component

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 4.3.5
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Due to a bug in Axis2, it seems that if one configure a SU to engage a specific module such as rampart (note: addressing is engaged globally by design, axis2 imposes it, and is disabled by service as needed), then it is actually used by all the services deployed on the component and not only for the given SU.

    This is caused by the following bug from Axis2: https://issues.apache.org/jira/browse/AXIS2-5721

    It is too complex to be worked around in Petals: at worst, service invocation may be a little bit slower, but normally there won't be any problem.
    We should wait for the bug to be fixed by upstream.

    Show
    Due to a bug in Axis2, it seems that if one configure a SU to engage a specific module such as rampart (note: addressing is engaged globally by design, axis2 imposes it, and is disabled by service as needed), then it is actually used by all the services deployed on the component and not only for the given SU. This is caused by the following bug from Axis2: https://issues.apache.org/jira/browse/AXIS2-5721 It is too complex to be worked around in Petals: at worst, service invocation may be a little bit slower, but normally there won't be any problem. We should wait for the bug to be fixed by upstream.
  • Environment:
    -

Activity

Victor NOËL made changes - Wed, 16 Sep 2015 - 16:15:27 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]

People

Dates

  • Created:
    Wed, 16 Sep 2015 - 16:15:17 +0200
    Updated:
    Wed, 16 Sep 2015 - 16:15:27 +0200