July 2018 - Apiman-user - Jboss List Archives

by Marc Savy

Hi All, Apiman 1.5 has been released. It contains an important new policy feature: the ability to modify policy failures before they are returned to users. This means that policies such as CORS can add their headers, irrespective of whether the request was successful or not (e.g. due to rate limiting). Blog post soon! Vert.x (Gateway Only): http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-vertx-1.5.0.F... WF10/EAP7.1: http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-wildfly10-1.5... WF11: http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-wildfly11-1.5... EAP7: http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-eap7-1.5.0.Fi... Tomcat 8+: http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-tomcat8-1.5.0... Regards, Marc

5 years, 8 months

1
3
0 / 0

Feedback wanted: Allowing policies to modify PolicyFailures emitted by *other* policies in chain

by Marc Savy

Marvin Oßwald filed a really interesting issue: https://issues.jboss.org/browse/APIMAN-1300 In short, if we imagine a policy chain like this: [CORS, PolicyA, PolicyB] Even if PolicyB emits a failure, then the CORS policy would likely still want to be able to process the PolicyFailure to add the relevant headers (otherwise a SPA type app like Angular would break). This seems like a valid use-case. Ideally I'd like to tackle this without breaking any existing interfaces. A couple of quick ideas: * Add a new interface that policies like CORS could implement that indicates it wants to do this kind of processing. E.g. IFailureProcessor or similar with a simple method signature like #process(PolicyFailure failureToModify). * An annotation: essentially the same as above, but with a @WhateverWeCallIt annotation on the method that does the processing.

5 years, 9 months

1
3
0 / 0

Blog: Customising path patterns for your Apiman Gateway

by Marc Savy

=After having a couple of requests on the topic of customising Apiman Gateway paths, I thought I'd write a blog: http://www.apiman.io/blog/apiman/gateway/manager/plugin/extensibility/201... This same concept works for plugins all throughout Apiman. Regards, Marc

5 years, 9 months

1
0
0 / 0

1.4.3.Final is out!

by Marc Savy

A couple of bugs fixed, including the Vert.x Gateway being unable to load plugins from its static config. Thanks for your contributions, everyone! http://www.apiman.io/blog/apiman/release/2018/07/03/release-1.4.3.html Regards, Marc p.s. We released 1.4.2.Final but due to my release VM having some kind of time issues (it was stuck on 28th June!) we immediately released 1.4.3.Final to ensure accurate metadata.

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Apiman-user July 2018