Hello Ruwan,
thanks, this is great! I will try this. Do I need Rampart 1.4 snapshot
as pointed out in one comment of the issue?
Thanks,
Jens
Ruwan Linton (JIRA) schrieb:
[
https://issues.apache.org/jira/browse/SYNAPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-127.
----------------------------------
Resolution: Fixed
Fixed... :)
Now synapse proxy services support different in and out message policies, the
modified configuration for the policy elements are;
<policy key="string" [type=("in" | "out")] />
if the type attribute is not present (the earlier syntax) is taken as the service level
policy and the type="in" implies in message policy and the out implies the out
message policy inside proxy.
I am planing to improve this to support operation level policies as well, for
the moment these are for all the operations :)
Ruwan
Should be able to define seperate policies for incoming and outgoing messages
-----------------------------------------------------------------------------
Key: SYNAPSE-127
URL: https://issues.apache.org/jira/browse/SYNAPSE-127
Project: Synapse
Issue Type: Improvement
Components: Proxy Services
Affects Versions: 1.1-QA-B1, 1.1.1-QA-B1
Reporter: Ruwan Linton
Assignee: Ruwan Linton
Fix For: 1.2, 1.1-QA-B1
It should be able to specify different policies for incoming and outgoing messages in proxy services
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
