synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton" <ruwan.lin...@gmail.com>
Subject Re: [jira] Resolved: (SYNAPSE-127) Should be able to define seperate policies for incoming and outgoing messages
Date Fri, 21 Mar 2008 20:48:20 GMT
Hi devs,

I have just added the operation level policies as well.

<policy key="string" [type=("in" | "out")] [operationName="string"]
[operationNamespace="string"]/>


   - if only the type is provided the specified type of the message of
   all the operations will be added with the policy


   - if only the operationName (and operationNamespace) is present then
   it is considered as operation policy and both in and out message will be
   applied with the specified policy
   - if both operation and message is specified the type of the message
   of the operation specified will be affected by the policy

Thanks,
Ruwan

On Mon, Mar 17, 2008 at 1:51 PM, Ruwan Linton <ruwan.linton@gmail.com>
wrote:

> Yes jens,
>
> Current svn trunk of synapse depends on rampart-SNAPSHOT anyway. So if
> you build synapse to try this, you will get that automatically.
>
> Thanks,
> Ruwan
>
> On 3/17/08, Jens Goldhammer <goldhammerdev@googlemail.com> wrote:
> > 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: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
>
> --
> Sent from Gmail for mobile | mobile.google.com
>
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>



-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Mime
View raw message