Re: Service chaining

Hi, With the current implementation a property is used to specify the out/receiving sequence. Property name is RECEIVING_SEQUENCE. In the send mediator this property is set to the appropriate sequence. In the injectMessage method of SynapseEnvironment we look for this property and if it is presen

Re: Service chaining

I think we should use an outSequence stack just like a fault stack. So if you specify any new outSequence in the case of proxy the proxy outSequence wont be overridden but will be pushed by the new one. And we need to change the way proxy out sequence is being picked by the callback receiver. Tha

Re: Constant/reproducable order of elements in synapse.xml

Hi Eric, Just an idea. Since Synapse XML is another XML, you should be able to use C14N and compare the two Synapse.xml files? Is it possibble? Thanks, Supun.. On Tue, Nov 10, 2009 at 3:50 AM, Ruwan Linton wrote: > Hi Eric, > > I was on vacation and just got back. :-) Going through my email bac

Re: Implementing Type Support for the Property Mediator

Hi Ruwan, I know everyone was busy. As you know, I never forced anybody to apply patches or anything like that :). Or I never even complained about something like that. But as a community it is not good to leave the patches behind. That is all I wanted to point out :). Thanks, Supun.. On Tue, No

Re: Constant/reproducable order of elements in synapse.xml

Hi Eric, I was on vacation and just got back. :-) Going through my email backlog. So, First of all I do not understand the issue that you are facing with the order. I agree that synapse serializes according to a hard order while builders do not expect that order. There is no specific reason to ha

Re: Service chaining

Yes, that makes me uncomfortable as well :). But I'm not sure how else we can get this across proxy services and message mediation. Any ideas please? Thanks, Supun.. On Tue, Nov 10, 2009 at 3:13 AM, Ruwan Linton wrote: > First of all, good idea... but the last comment on proxy services didn't >

Re: Service chaining

First of all, good idea... but the last comment on proxy services didn't make me comfortable, it is confusing to the users. Thanks, Ruwan On Mon, Nov 9, 2009 at 1:42 PM, Supun Kamburugamuva wrote: > On Mon, Nov 9, 2009 at 1:27 PM, Hiranya Jayathilaka > wrote: > >> +1 >> >> Looks good to me but

Re: Implementing Type Support for the Property Mediator

> > What I wanted to say was making the people who submit patches go after > developers is not a good practice in any Apache project and I don't think > there are lot of people who are willing to submit patches and go after > developers. > > Anyway thanks for bringing these points :). > > Thanks, >

[jira] Commented: (SYNAPSE-595) Possible race condition in ConnectionPool implementation of nhhtp transport

[ https://issues.apache.org/jira/browse/SYNAPSE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775112#action_12775112 ] Supun Kamburugamuva commented on SYNAPSE-595: - HI Asanka, I agree with you.

Re: Implementing Type Support for the Property Mediator

Hi Hiranya > To solve this problem I would like to propose adding a new attribute > to the property mediator. The new attribute, named 'type' will allow > specifying a type for the parameter value. The property mediator will > make sure that the value is properly cast into the specified type > befo

Re: Implementing Type Support for the Property Mediator

Guys Could I please ask that you cut out the unwanted headers and footers of emails in future? I cannot easily read them, and thus am tempted to skip complicated threads like these - http://markmail.org/thread/g23jhjz3dpzfgjcc :-) cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlo

[jira] Resolved: (SYNAPSE-595) Possible race condition in ConnectionPool implementation of nhhtp transport

[ https://issues.apache.org/jira/browse/SYNAPSE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved SYNAPSE-595. --- Resolution: Invalid Assignee: Asankha C. Perera Supun The reason why double c

Hudson build is back to stable: Synapse - Trunk #1387

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

Hudson build is back to stable: Synapse - Trunk » A pache Synapse - Non-blocking HTTP/s Transport #1387

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

[jira] Assigned: (SYNAPSE-575) improve the callout mediator to provide the EPR as an endpoint.

[ https://issues.apache.org/jira/browse/SYNAPSE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] indika priyantha kumara reassigned SYNAPSE-575: --- Assignee: indika priyantha kumara > improve the callout mediator to

[jira] Commented: (SYNAPSE-539) Retrieving policies from the WSDL for WSDL Endpints

[ https://issues.apache.org/jira/browse/SYNAPSE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775043#action_12775043 ] indika priyantha kumara commented on SYNAPSE-539: - Patch can not be applie

[jira] Assigned: (SYNAPSE-539) Retrieving policies from the WSDL for WSDL Endpints

[ https://issues.apache.org/jira/browse/SYNAPSE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] indika priyantha kumara reassigned SYNAPSE-539: --- Assignee: indika priyantha kumara > Retrieving policies from the WSD

Hudson build is still unstable: Synapse - Trunk #1386

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

Hudson build is still unstable: Synapse - Trunk » A pache Synapse - Non-blocking HTTP/s Transport #1386

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

Re: Implementing Type Support for the Property Mediator

On Mon, Nov 9, 2009 at 1:50 PM, Supun Kamburugamuva wrote: > > > On Mon, Nov 9, 2009 at 1:35 PM, Hiranya Jayathilaka > wrote: > >> >> >> On Mon, Nov 9, 2009 at 1:26 PM, Supun Kamburugamuva wrote: >> >>> >>> >>> On Mon, Nov 9, 2009 at 1:12 PM, Hiranya Jayathilaka < >>> hiranya...@gmail.com> wrote:

Re: Implementing Type Support for the Property Mediator

On Mon, Nov 9, 2009 at 1:35 PM, Hiranya Jayathilaka wrote: > > > On Mon, Nov 9, 2009 at 1:26 PM, Supun Kamburugamuva wrote: > >> >> >> On Mon, Nov 9, 2009 at 1:12 PM, Hiranya Jayathilaka > > wrote: >> >>> >>> >>> On Mon, Nov 9, 2009 at 12:45 PM, Supun Kamburugamuva >>> wrote: >>> O

Re: Service chaining

On Mon, Nov 9, 2009 at 1:27 PM, Hiranya Jayathilaka wrote: > +1 > > Looks good to me but can we please change the 'receivingSequence' attribute > to something more appropriate? How about 'responseSequence'? Also I think > this feature can be further generalized without restricting it as a service

Hudson build became unstable: Synapse - Trunk #1385

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

Hudson build became unstable: Synapse - Trunk » Ap ache Synapse - Non-blocking HTTP/s Transport #1385

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

Re: Implementing Type Support for the Property Mediator

On Mon, Nov 9, 2009 at 1:26 PM, Supun Kamburugamuva wrote: > > > On Mon, Nov 9, 2009 at 1:12 PM, Hiranya Jayathilaka > wrote: > >> >> >> On Mon, Nov 9, 2009 at 12:45 PM, Supun Kamburugamuva >> wrote: >> >>> >>> >>> On Mon, Nov 9, 2009 at 12:25 PM, Hiranya Jayathilaka < >>> hiranya...@gmail.com>