Skip to content
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

Feature/enable choosing bindings #19

Closed
wants to merge 25 commits into from

Conversation

ghareeb-falazi
Copy link
Member

This pull request allows users to configure the gateway so that the output binding (i.e., the format of the SCIP reply messages) correspond to their expectations. Two output bindings are currently supported: json-rpc and camunda

ghareeb-falazi and others added 25 commits February 22, 2022 12:09
- Add Camunda tests for subscribe method
- Fix EthereumAdapter test
- Fix dependencies
- Initial support for asynchronous errors
- Fix tests
- Switch BlockchainManager to using the new mechanism
- Introduce GenericAsynchronousBalException
- Add test cases
- Reorganize packages
- Use a dedicated final class to represent asynchronous exceptions. It encapsulates a BalException as a cause, and adds an obligatory correlation identifier. The class should be instantiated only by the blockchain manager because it knows the context + it has the correlation identifier.
- detect block gas limit reached
- detect unknown account
- possibly many more errors...
- all use -32100 code because details are only available in a string not a code.
- if the timeout value is specified to be 0 (or was missing), it is set to Long.MAX_VALUE
- Add RESTful controller for managing endpoint binding rules at the "bindings" path
- write README.md entry
Catch all exceptions (instead of only IOException) inside the Observable that fetches Ethereum blocks (otherwise the error will not be handled and will cause a failure "missing onError bla bal")
- fix message names
- fix data types
- update README
Remove ProcessInstanceID from Camunda Message
@ghareeb-falazi
Copy link
Member Author

Handled by #26

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