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

Bug in Client.newRpcStub(...) : Constructor may not allow NULL values #259

Open
longquanzheng opened this issue Oct 31, 2024 · 0 comments
Open

Comments

@longquanzheng
Copy link
Contributor

longquanzheng commented Oct 31, 2024

In the current implementation, in order to get a "Mock" of the workflow class, we use the first constructor, and pass all null values into the constructor to create he mock instance.

final Object[] params = new Object[parameterCount];

However, this may be a problem if the constructor doesn't allow NULL values.
See the example of broken experience here: #260

This is usually not a problem because usually the iwf workflow only need to take in a list of state or its dependency.

An idea is to now rely on the real constructor -- i there is a way to create the instance bypassing the real class constructor

@longquanzheng longquanzheng changed the title Bug in Client.newPpcStub(...) : Constructor may not allow NULL values Bug in Client.newRpcStub(...) : Constructor may not allow NULL values Oct 31, 2024
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

No branches or pull requests

1 participant