Petals BC SOAP

When engaging the module Rampart, the module Addressing is automatically engaged

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 4.0.8
  • Fix Version/s: 4.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When engaging the module Rampart or any other module except Adressing, the module Addressing is automatically engaged.

    See the class SoapSUManager.getModules(), svn#28969:

    private List<String> getModules(final ConfigurationExtensions extensions) {
	final List<String> result = new ArrayList<String>();

	// get modules from extension
	final String token = extensions.get(MODULES);

	if (token != null) {
		// get individual modules values
		final StringTokenizer st = new StringTokenizer(token, ",");
		result.add(Constants.MODULE_ADDRESSING);
		while (st.hasMoreTokens()) {
			result.add(st.nextToken().trim());
		}
	}
	return result;
}

    The module WS-Addressing is engaged when the parameter of the JBI descriptor modules is set.

    Show
    When engaging the module Rampart or any other module except Adressing, the module Addressing is automatically engaged. See the class SoapSUManager.getModules(), svn#28969: 
    private List<String> getModules(final ConfigurationExtensions extensions) {
	final List<String> result = new ArrayList<String>();

	// get modules from extension
	final String token = extensions.get(MODULES);

	if (token != null) {
		// get individual modules values
		final StringTokenizer st = new StringTokenizer(token, ",");
		result.add(Constants.MODULE_ADDRESSING);
		while (st.hasMoreTokens()) {
			result.add(st.nextToken().trim());
		}
	}
	return result;
}
    The module WS-Addressing is engaged when the parameter of the JBI descriptor modules is set.
  • Environment:
    -

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Thu, 15 Dec 2011 - 16:02:03 +0100 - edited

As mentionned in PETALSBCSOAP-96:

Already fixed in the version 4.1.

The module is always engaging in Axis2 as it is only possible to engage it globally (http://axis.apache.org/axis2/java/core/docs/adv-userguide.html). Thus it is not possible to control it with the parameter modules.

But it is possible to enable/disable the WS-Addressing for a specific service with the parameter enable-wsa in the version 4.1 (By default, it is disabled).

So, the module 'addressing' must be always engaged, add should be automatically added if the module list does not contain it.

Show
Christophe DENEUX added a comment - Thu, 15 Dec 2011 - 16:02:03 +0100 - edited As mentionned in PETALSBCSOAP-96:
Already fixed in the version 4.1. The module is always engaging in Axis2 as it is only possible to engage it globally (http://axis.apache.org/axis2/java/core/docs/adv-userguide.html). Thus it is not possible to control it with the parameter modules. But it is possible to enable/disable the WS-Addressing for a specific service with the parameter enable-wsa in the version 4.1 (By default, it is disabled).
So, the module 'addressing' must be always engaged, add should be automatically added if the module list does not contain it.

People

Dates

  • Created:
    Tue, 18 Oct 2011 - 13:28:00 +0200
    Updated:
    Thu, 16 Feb 2012 - 17:06:33 +0100
    Resolved:
    Thu, 15 Dec 2011 - 16:05:53 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.