Hi Hiranya,
Thanks for the suggestion.. will try that out...
Another issue I found with ESB sample 800 on API..
If you open up the sample configuration file... Then you will see the
following..
<resource url-pattern="/order/*" methods="POST">
But, when you load that configuration in to the ESB and go to the source
view you will find url-pattern="/order/*" is missing...
Is this a known issue.. any reason behind this...
Thanks & regards,
-Prabath
On Mon, Feb 27, 2012 at 12:15 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote:
> BTW Prabath, ideally we should be able to implement your use case using
> the URL mapping "/library/books/*". This should accept all URLs (with all
> combinations of query params) you're interested in. But this didn't work in
> the first cut implementation I did. I myself came across this scenario
> while working on samples so I've fixed it in Synapse trunk. So if you're
> using the latest Synapse core source from the Apache trunk, above URL
> mapping is all you want to make this scenario work. You can access query
> params using the XPath "query.param.{paramName}"
>
> Thanks,
> Hiranya
>
>
> On Sun, Feb 26, 2012 at 11:22 AM, Prabath Siriwardena <prab...@wso2.com>wrote:
>
>> On Sun, Feb 26, 2012 at 11:08 AM, Udayanga Wickramasinghe
>> <udaya...@wso2.com> wrote:
>> >
>> >
>> > On Sat, Feb 25, 2012 at 7:53 PM, Hiranya Jayathilaka <hira...@wso2.com>
>> > wrote:
>> >>
>> >>
>> >>
>> >> Sent from my iPhone
>> >>
>> >> On Feb 25, 2012, at 5:05 AM, Prabath Siriwardena <prab...@wso2.com>
>> wrote:
>> >>
>> >> Hi Hiranya,
>> >>
>> >> Thanks for the input..
>> >>
>> >> BWT won't this create some limitations.. specially in the API
>> Gateway...
>> >>
>> >>
>> >> It is a limitation. We should iteratively implement support for higher
>> >> level uri templates.
>> >
>> > +1
>> > there are multiple level of constructs that is supported by uri
>> templates ,
>> > which we will be able to support iteratively
>> > for example in this case following uri template can be used..
>> > /library/book{?author,name}
>>
>> +1. As per Hiranya.. /library/book{?author,name}... this we don't
>> support yet.. I believe we can live without it for the API Gateway
>> first release..
>>
>> BTW what is our plan for iterative improvements?
>>
>> Thanks & regards,
>> -Prabath
>>
>> >
>> > Regards,
>> > udayanga--
>> >
>> > Udayanga Wickramasinghe
>> > Software Engineer; WSO2 Inc.; http://wso2.com,
>> > email: udaya...@wso2.com cell: +94 (77) 983-4365
>> > blog: http://udayangawiki.blogspot.com
>> > twitter: http://twitter.com/udayanga_wick
>> >
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.; http://wso2.org
> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
--
Thanks & Regards,
Prabath
Mobile : +94 71 809 6732
http://blog.facilelogin.com
http://RampartFAQ.com
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
