You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, my intent is to user Membrane as a service hub within Tomcat.
Therefore, I need to differentiate services by URL prefix, not by TCP port, which I usually do like this:
Same result. Interesting question: How should swaggerRewriter know which URL to prefix to swaggerJson in order to fetch it? The default of "swagger.json" does not suffice. So I probably need to give a full URL:
Yes there is a bug, in SwaggerProxyKey. It work as
<serviceProxy`` port="8000"> <swaggerRewriter swaggerJson="https://petstore.swagger.io/v2/swagger.json" /> <target host="petstore.swagger.io" port="443" /> </serviceProxy>
For swaggerProxy, I will write the patch
I tried using the petstore swagger example from the examples:
That itself works fine - although the services themselves are not accessible, either (like http://localhost:8080/ works while http://localhost:8080/v2/pet/8 does not).
However, my intent is to user Membrane as a service hub within Tomcat.
Therefore, I need to differentiate services by URL prefix, not by TCP port, which I usually do like this:
I have found no way to use swaggerProxy like soapProxy with different paths pointing to several backend services like this:
It seems that swaggerProxy itself does not support a path element.
When I try to use an equivalent serviceProxy with swaggerRewriter instead, it does not work either way:
Gives an exception saying: "com.predic8.membrane.core.resolver.ResourceRetrievalException: null while retrieving swagger.json".
Same result. Interesting question: How should swaggerRewriter know which URL to prefix to swaggerJson in order to fetch it? The default of "swagger.json" does not suffice. So I probably need to give a full URL:
and indeed, that works.
But when I try to combine that with path, it goes horribly wrong, neither:
nor
nor the other way around:
work.
But maybe I am doing it wrong?
The text was updated successfully, but these errors were encountered: