Skip to content

Add reactive backend support #998

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

injectives
Copy link
Contributor

This update brings reactive backend support.

Its scope is limited to providing partial transparent support for existing test cases. More updates are expected in future PRs.

@injectives injectives force-pushed the feature/transparent-reactive-backend branch from 44f1b73 to 5e9545c Compare September 3, 2021 15:38
This update brings reactive backend support.

Its scope is limited to providing partial transparent support for existing test cases. More updates are expected in future PRs.
@injectives injectives force-pushed the feature/transparent-reactive-backend branch from 5e9545c to ddf14e0 Compare September 3, 2021 15:39
@injectives injectives requested a review from gjmwoods September 3, 2021 15:40
Copy link
Contributor

@gjmwoods gjmwoods left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎺

@injectives injectives merged commit 6ee3936 into neo4j:4.4 Sep 6, 2021
@injectives injectives deleted the feature/transparent-reactive-backend branch September 6, 2021 08:40
injectives added a commit to injectives/neo4j-java-driver that referenced this pull request Sep 6, 2021
This update brings reactive backend support.

Its scope is limited to providing partial transparent support for existing test cases. More updates are expected in future PRs.
injectives added a commit to injectives/neo4j-java-driver that referenced this pull request Sep 6, 2021
This update brings reactive backend support.

Its scope is limited to providing partial transparent support for existing test cases. More updates are expected in future PRs.
injectives added a commit that referenced this pull request Sep 6, 2021
* Add support for Resolver and DomainNameResolver to async Testkit backend (#992)

* Decouple TestkitState from CommandProcessor. (#993)

This commit remoces the command processor from the TestKit state. The processor is supposed to use that state, not to be part of it.
However, some requests, like `NewDriver` need the processor to trigger further state.
Therefor the processor is now provided as injectable value via Jackson, so that any request can indicate that it needs a processor via a constructor argument.

* Remove unnessary Lombok noise. (#995)

* Migrate Testkit backend to Netty implementation (#994)

* Migrate Testkit backend to Netty implementation

* Remove unnessary Optional in processAsync.

This brings both sync and asynchronous paths in TestKitState in symmetry.
In addition, I noticed that the transaction related tests behaved differently in sync and async (when a tx is not found). I fixed that.

* Remove redundant lines

Co-authored-by: Michael Simons <[email protected]>

* Add reactive backend support (#998)

This update brings reactive backend support.

Its scope is limited to providing partial transparent support for existing test cases. More updates are expected in future PRs.

Co-authored-by: Michael Simons <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants