You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2006/04/17 00:07:51 UTC
[jira] Commented: (SM-397) WSA:Action header should override
default service/endpoint values from the http endpoint definition
[ https://issues.apache.org/activemq/browse/SM-397?page=comments#action_36057 ]
Guillaume Nodet commented on SM-397:
------------------------------------
Changing this behavior at this point would break compatibility.
As a workaround, you should define the targetInterfaceName attribute of the endpoint to a dummy name.
This information will be overriden by the wsa:Action header and service / endpoint informations defined on the endpoint won't be used.
> WSA:Action header should override default service/endpoint values from the http endpoint definition
> ---------------------------------------------------------------------------------------------------
>
> Key: SM-397
> URL: https://issues.apache.org/activemq/browse/SM-397
> Project: ServiceMix
> Type: Bug
> Components: servicemix-http
> Versions: 3.0-M2
> Reporter: Ilya Kuleshov
>
>
> Manual says that although service and endpoint attributes are required
> by the consumer endpoint definition of http-component, it is possible
> to use WS-Addressing to set custom target for the SOAP message. When I
> use the WSA:To header then value from this header overrides default
> service/endpoint correctly.
> On the other side, when I use the WSA:Action header then
> http-component sets destination interface/operation attributes of the
> message as expected but leaves service/endpoint attributes from the
> http endpoint definition. This results into routing problems because
> the JBI message now has interface, operation, service and endpoint
> attributes set altogether.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira