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.
6 years
Help needed: Feedback/testing for Apiman on ES 5.x (and possibly ES 2.x)
by Marc Savy
Hi,
After spending the last week or more fiddling with test harness and CI
issues, we finally seem to be (almost) there.
I'd appreciate anyone who could test the latest an ES 5.x version of
Apiman for me. It still needs some tidying up, but should be
functional.
Steps:
git clone git@github.com:msavy/apiman.git
git checkout es5x
mvn clean install
cd distro/{distro of your choice}/target/{distro overlay zip of your choice}
handle the distro zip as you usually would a release (i.e. extract
overlay onto a server such as wildfly10)
Please modify apiman.properties to match your particular configuration
and try things out!
Regards,
Marc
6 years, 1 month
