IMHO we should not bound to swagger as most important thing is run time
dispatching.
As i understood swagger does not follow any well defined specification.
So bound to something like that would be useless and make things
complicated.
And on the other hand swagger UI is just use for testing purposes and most
of users call service using some kind of client.
Other important thing we should focus is define resources which do not
accept query parameters.
In practical scenarios we may have services which do not accept query
parameters.
So when we implement this we need to focus on both scenarios.
01. Query parameters are optional
02. No query parameters.
And other important usage of * is create APIs for services which does not
implemented completely.
As example we can have this kind of resource
/bookStore/{bookID}*
In future backend service implementation may have
/bookStore/{bookID}/move
/bookStore/{bookID}/transfer
etc.
So its not necessary query parameters but those are control verbs in
resource path(no query parameters).
So we may need to focus on that aspect as well.
Thanks,
sanjeewa.
On Thu, Oct 22, 2015 at 12:00 PM, Joseph Fonseka <[email protected]> wrote:
>
>
>> Do you think we can migrate Resources of APIs which have been defined
>> with * without breaking existing clients?
>>
>
> For API manager it is possible but this affects the existing ESB users as
> well for them it would be a manual migration.
>
> 4. Support full URI Templates in ESB and only support what is supported in
>>> swagger in API Manager.
>>>
>>
>> I don't think it's a good idea to limit ourselves to what swagger
>> supports.
>>
>
> Yes that make sense going forward swagger might adopt the URI Templating.
> If so we have following two options.
> 1. Do nothing and clearly inform users if unsupported URITemplate is used
> it will not work properly with swagger console.
> 2. Use swagger vendor extension to give support to unsupported url
> template.
> Ex. In swagger we can use an attribute like "x-uri-template"
> under a resource which will be used to create the resource in synapse.
>
> Regards
> Jo
>
>
>
>> *Joseph Fonseka*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 772 512 430
>>> skype: jpfonseka
>>>
>>> * <http://lk.linkedin.com/in/rumeshbandara>*
>>>
>>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : [email protected]
>> Phone : +94 777 775 729
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * <http://lk.linkedin.com/in/rumeshbandara>*
>
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/
<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
