Would be possible to upgrade APIMan from 1.2.8 to 1.3.0?
by Celso Agra
Hi all,
Sorry about that, but I'm concern to upgrade my apiman to a newest.
I read about upgrating the application:
http://www.apiman.io/latest/installation-guide.html#_upgrading_to_a_new_a...
But I'd like to know if I upgrade from 1.2.8 to 1.3.0 is must needed to
export and reimport all data from different versions.
Could I just change server and application without change anything in my
database? just put the new wildfly running the apiman instance. Would be
possible to do that?
PS.: My APIMan is running with a remote database and remote Keycloak.
Best Regards,
--
---
*Celso Agra*
9 years
Response when gateway cannot connect to the API implementation
by Scott Elliott
Right now, when the APIMAN gateway cannot connect to the API
implementation's endpoint, the response code is 500, the message is null,
and there is a stack trace. It's not a very useful response for the
caller, and it's not really an internal problem with the gateway. It would
be better if another response code were used (502? 503?) and a useful
message were returned instead of a stack trace.
9 years, 1 month
apiman 1.3.0.Final released!
by Marc Savy
Greetings Apilytes,
I'm pleased to officially announce the release of apiman 1.3.0.Final.
For more information, check out the blog post:
http://www.apiman.io/blog/apiman/release/2017/05/25/release-1.3.html
Some prominent changes:
- Vert.x gateway officially released! Please try it out and let us know
your experiences.
- Headless registry (load gateway config from local or remote JSON file).
- Documentation reworked and published in GitBook format (use the tabs in
the top right of certain pages to change between Servlet properties and
Vert.x JSON examples!).
- Lots of bug-fixes, features and enhancements.
- Performance tuning
Subsequent releases will occur more regularly from now, and you can expect
for more information to be released regarding 3scale integration in the
community as we're able to.
Regards,
Marc
9 years, 1 month
