capture response where servlet code programmatically starts async dispatch

[noffke]

Description

The GraphQL servlet from https://github.com/graphql-java-kickstart/graphql-java-servlet programmatically starts an async request by calling startAsync on the HttpServletRequest. In this case, logbook misses the reply because the logbook filter checks request.isAsyncStarted() before logging. In order to fix this issue, an AsyncListener is being registered whenever startAsync is being called.

Regarding LogbookAsyncListener, would it make sense to also implement the other methods besides onComplete? If yes, how?

Motivation and Context

Fix for issue #954

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[whiskeysierra]

First off, thank you for your contribution! 📣

Regarding LogbookAsyncListener, would it make sense to also implement the other methods besides onComplete? If yes, how?

I can't really judge, tbh.

[whiskeysierra]

👍

[whiskeysierra]

I released your fix as 2.6.2. Thanks a lot for your contribution! 🎉