Petals BC SOAP

Add the possibility to enable/disable WSA-Addressing in the provider role

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 4.0.4
  • Fix Version/s: 4.1
  • Component/s: None
  • Security Level: Public
  • Description:

    Add an extension to disable WSA-Addressing in the provider role

  • Environment:
    os: all

Activity

Hide
Christophe DENEUX added a comment - Fri, 19 Nov 2010 - 11:42:35 +0100

If you change a default, you introduce an incompatibility: SU edployed on 4.0.4 can't be deployed on 4.1 without updates. So, according to the version naming conventions, if you want to change the default value of the WSAdressing activation, you must to it in a version 5.0 because the version 4.1 must be compatible with 4.0.

Another solution is to introduce a new optional parameter: if present, it supersedes the default value

Show
Christophe DENEUX added a comment - Fri, 19 Nov 2010 - 11:42:35 +0100 If you change a default, you introduce an incompatibility: SU edployed on 4.0.4 can't be deployed on 4.1 without updates. So, according to the version naming conventions, if you want to change the default value of the WSAdressing activation, you must to it in a version 5.0 because the version 4.1 must be compatible with 4.0. Another solution is to introduce a new optional parameter: if present, it supersedes the default value
Hide
noddoux added a comment - Fri, 19 Nov 2010 - 11:00:51 +0100

There will not be a version 4.0.5 of the BC SOAP component but a version 4.1 because the WSA-Addressing will be disabled by default contrary to the version 4.0.4 where it is enabled by default.

Show
noddoux added a comment - Fri, 19 Nov 2010 - 11:00:51 +0100 There will not be a version 4.0.5 of the BC SOAP component but a version 4.1 because the WSA-Addressing will be disabled by default contrary to the version 4.0.4 where it is enabled by default.
Hide
Frédéric Gardes added a comment - Fri, 19 Nov 2010 - 10:10:47 +0100

Good job!
But I don't understand something: I'm currently using the 4.0.4 version, and the wsa-addressing is enabled by default (we lost times because of this: the external WS invoked had a problem with this appeared wsa-to element into the soap headers, and I didn't orient my researches on this way...).
Maybe this Jira is on the 4.0.5 version, not on 4.0.4 (already released)?

Show
Frédéric Gardes added a comment - Fri, 19 Nov 2010 - 10:10:47 +0100 Good job! But I don't understand something: I'm currently using the 4.0.4 version, and the wsa-addressing is enabled by default (we lost times because of this: the external WS invoked had a problem with this appeared wsa-to element into the soap headers, and I didn't orient my researches on this way...). Maybe this Jira is on the 4.0.5 version, not on 4.0.4 (already released)?
Hide
noddoux added a comment - Thu, 18 Nov 2010 - 18:22:09 +0100

A parameter soap:enable-wsa is added to the jbi.xml of a SU provide. The WSA-Addressing is disabled by default. To enable it, set the parameter to true.

Show
noddoux added a comment - Thu, 18 Nov 2010 - 18:22:09 +0100 A parameter soap:enable-wsa is added to the jbi.xml of a SU provide. The WSA-Addressing is disabled by default. To enable it, set the parameter to true.

People

  • Assignee:
    noddoux
    Reporter:
    noddoux
  • Watchers:
    0

Dates

  • Created:
    Thu, 18 Nov 2010 - 18:20:44 +0100
    Updated:
    Thu, 16 Feb 2012 - 17:06:37 +0100
    Resolved:
    Thu, 18 Nov 2010 - 18:22:36 +0100