synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-525) Option to preserve addressing headers should be available
Date Sun, 10 May 2009 18:22:45 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707822#action_12707822
] 

Andreas Veithen commented on SYNAPSE-525:
-----------------------------------------

As already said above, I don't think that preserving the WS-Addressing headers by default
is a good idea. This change breaks many of the Synapse samples and will therefore also break
lots of existing user configurations. I just discovered that sample 251 is also broken because
of this. It now fails with the following error in the sample Axis2 server:

org.apache.axis2.AxisFault: A header representing a Message Addressing Property is not valid
and the message cannot be processed
  at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:373)
  at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionMismatchFault(AddressingFaultsHelper.java:222)
  at org.apache.axis2.handlers.addressing.AddressingInHandler.extractActionInformation(AddressingInHandler.java:532)
  at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:238)
  at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:153)
  at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
  at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
  at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:314)
  at org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(JMSMessageReceiver.java:215)
  at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(JMSMessageReceiver.java:126)
  at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(ServiceTaskManager.java:512)
  at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:424)
  at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  at java.lang.Thread.run(Thread.java:613)

Ruwan, can you please work on this?

> Option to preserve addressing headers should be available
> ---------------------------------------------------------
>
>                 Key: SYNAPSE-525
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-525
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2
>         Environment: all env
>            Reporter: Ruwan Linton
>            Assignee: Ruwan Linton
>             Fix For: 1.3
>
>
> For the moment Synapse replaces all the addressing headers when sending the message out
to the routed service, but there can be case where the mediation configuration should preserve
the addressing headers. For example like wsa:Reply-To
> So this requires a switch to configure the send mediator to not to alter addressing headers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message