May 2017 - Apiman-user - Jboss List Archives

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*

6 years, 10 months

3
13
0 / 0

Future of APIMan (in the context of recent announcements)?

by Donovan Muller

Hi all, Having seen the response (from Marc Savy) on the thread with the subject "Response when gateway cannot connect to the API implementation" about a 1.3.0 release of APIMan (with the vert.x gateway) and then having seen related commits on the GitHub repo ( https://github.com/apiman/apiman/commit/d3cedc5e05f143d45df8aa065e61de40b...). I'd just like to ask about the future of APIMan in relation to the 3Scale integration, especially, considering this announcement in relation to OpenShift: https://www.redhat.com/en/about/press-releases/red-hat-introduces-fully-c... . Some questions I have: * Will APIMan form some part of the new 3Scale integration (more specifically, the on premise solution/OpenShift)? * If not, why the 1.3.0 release (since this adds new features)? * If so, what would APIMan be used for? I'm asking this in the context of a financial services organisation needing an on premise OpenShift integrated API Gateway solution. We are currently using APIMan (based on what was done here: https://github.com/openshift/origin-apiman) as a temporary solution until whatever 3Scale on premise solution will be released... Thanks in advance

6 years, 11 months

3
5
0 / 0

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.

6 years, 11 months

4
6
0 / 0

Any objections to retiring the WildFly 8 & 9 distros of apiman?

by Marc Savy

Hi, Both of these versions are quite old and the quality has been suffering accordingly. If nobody has objections I'm going to retire the WF 8 and 9 distros. WF10 (and soon 11) and EAP should continue to be supported. Regards, Marc

6 years, 11 months

3
2
0 / 0

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

6 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Apiman-user May 2017