Hi all,

I'm working on pulling a demo together based on $subject. So, good news is
that it works nearly perfectly. But, then there were a few things that I
noted.

   1. API-M is unable to process the Swagger URL presented by MSF4J (due to
   inverted commas, AFAIU).
   2. It parses the Swagger file well, but there were two issues:
      1. It uses the Title and the default one presented by MSF4J has
      spaces and won't work - (so had to fix the sample - but that's fine).
      2. It doesn't extract the context from the Swagger file
      appropriately, but appends that into the resources on the API definition.
      So, if you stick to the defaults, the URL looks a little ugly, "
      http://localhost:8280/*stockquote*/1.0/*stockquote*/IBM";

Are these things for which we have fixes/workarounds?

Thanks,
Senaka.
-- 


*[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
Solutions Architect; WSO2 Inc.; http://wso2.com



*Member; Apache Software Foundation; http://apache.org
<http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +44 203
318 6025;*


*M: +44 782 741 1966Linked-In: http://linkedin.com/in/senakafernando
<http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to