On Nov 24, 2014, at 5:51 PM, Vishvjit Khalipe <[email protected]> wrote:
> Hello, > > I have few questions related to REST API Proxy > > 1. Should we use <proxy> or <api> for proxying existing REST API? I think you're better off with APIs. Proxy services are best with SOAP services. > 2. Is there a way to proxy swagger api docs ? If I use simple URL redirect > for API docs, I get ClassCastException: > org.apache.axiom.om.impl.llom.OMTextImpl cannot be cast to > org.apache.axiom.om.OMElement I've left a comment on the other thread regarding this. > 3. Is it possible to use context template for API ? I want to have > different tentent name in the URL so want to have dynamic context. (I can > use url-template for dynamic url but I am wondering if context can be > dynamic as well. No, Synapse currently doesn't support this feature. > 4. What are the best practices of proxying existing REST API? Depends on what kind of mediation logic you wish to implement in your APIs. Other than that, typical Synapse best practices apply (e.g. use separate reusable sequences and endpoints when possible) > 5. Are there any examples of proxying rest api ? The samples and blogs have > discuss rest proxy for soap services. Not in the current documentation. But I'm sure folks at WSO2 have published several articles on this subject (may be one of them on the mailing list can point you in the right direction). Thanks, Hiranya > -- > Regards, > Vish -- Hiranya Jayathilaka Mayhem Lab/RACE Lab; Dept. of Computer Science, UCSB; http://cs.ucsb.edu E-mail: [email protected]; Mobile: +1 (805) 895-7443 Blog: http://techfeast-hiranya.blogspot.com
