pscheidl / fortee Goto Github PK

• Semisafe interceptor may let declared exceptions through automatically.

Extend current @Failsafe interceptor with optional circuit breaker functionality.

• User-defined number of fails
• User-defined retry window

ExecutorService.invokeAll() + ExecutorService.invokeAny() methods are non-blocking and should be blocking.

http://aspects.jcabi.com/annotation-unitedthrow.html

An interesting concept. Instead of forcing Optional, conversion into one allowed exception happens. Could be extension of current Failsafe annotation.

Methods annotated with @Failsafe may not declare any Throwables. This can be checked at startup.

http://www.lordofthejars.com/2015/11/java-ee-gradle-and-integration-tests.html

Introduce new annotation for timeouts - @timeout tied to an interceptor.

• Basic algorithm for timeout is strict user-defined deadline. The timeout is defined once per annotation.

Both methods and classes can be annotated.

Failsafe interceptor should fire information event every time an error is caught.

• Wait for CDI 2.0 Async events ?

• End-to-end monitoring per-request context.
• Consider feasibility of having monitoring points (subroutines of execution), where execution time is measured.

Methods annotated with @SemiSafe may not be able to declare throwing any other exceptions and errors than the ones listed in the annotation itself.

This can be checked during startup.

suggesting to rename the class BenguardLogger to FortLogger (or ForteeLogger).

Methods other than submit* are only delegated, but not properly overridden.

Workaround for @Failsafe interceptor not being activated in Glassfish-based AS. https://java.net/jira/browse/GLASSFISH-21718 / payara/Payara#1532.

Jakarta EE 8 has been released. Tests are using old WildFly 11, but there is Jakarta EE 8 certified WildFly 17. Create tests for JakartaEE 8 and do the necessary compatibility changes, if any.

@Failsafe annotation converts all exceptions thrown into Optional. Consider implementing a functionality that:

1. Lets any exception defined through, without catching it.
2. Allow using stereotypes to define exception passing ?