[
https://issues.apache.org/jira/browse/SYNAPSE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-128.
----------------------------------
Resolution: Fixed
Fixed in the current SVN head.
I had to go for a different handler, if we use the SynapseDispatcher to mark
these unprocessed MustUnderstand headers messages coming to proxy services will
not get this functionality because those messages never arrive
SynapseDispatcher.
Added a sample to elaborate this functionality (sample 105)
> Synapse should be able to just rout the messages to the destination without
> processing the security headers
> -----------------------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-128
> URL: https://issues.apache.org/jira/browse/SYNAPSE-128
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
> Fix For: 1.1
>
>
> Currently synapse does not get the message if it is not processing the
> security headers because Axis2 throws a MustUnderstand exception before the
> message arrives in to synapse.
> Synapse should be able to just route the messages to the destination without
> processing the security like must understand headers.
> As Jose proposed, solution for this would be to add a custom handler to set
> these must understand flags off before receiving the message to the
> AxisEngine. This handler should come after the SynapseDispatcher, or else can
> SynapseDispatcher itself do the trick?.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
