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

Add possibility for Tuples as return types to dbus method calls #149

Merged
merged 1 commit into from
Sep 8, 2021

Conversation

poeschel
Copy link
Contributor

@poeschel poeschel commented Sep 8, 2021

In dbus it is possible for a method to have multiple return types. To
map this into the java world, the dbus-java library wraps the return
types into a class, that contains all desired values as fields. This
class extends the Tuple class and is normally generated by the
InterfaceCodeGenerator.
There was a piece missing in the library, that could deal with such
Tuples as a return type to a dbus method call.
This commit adds the missing piece and a little test case.

In dbus it is possible for a method to have multiple return types. To
map this into the java world, the dbus-java library wraps the return
types into a class, that contains all desired values as fields. This
class extends the Tuple class and is normally generated by the
InterfaceCodeGenerator.
There was a piece missing in the library, that could deal with such
Tuples as a return type to a dbus method call.
This commit adds the missing piece and a little test case.
@hypfvieh hypfvieh merged commit 89a0f77 into hypfvieh:master Sep 8, 2021
hypfvieh added a commit that referenced this pull request Sep 14, 2021
…Class<?> type[0]) caused class cast exception because type[0] is casted to Class<?> even if type[0] is not compatible with Class<?>; The issue was visible in TestCross but test cross still succeeded because the assert was not called in junit test runner thread
hypfvieh added a commit that referenced this pull request Sep 14, 2021
…Class<?> type[0]) caused class cast exception because type[0] is casted to Class<?> even if type[0] is not compatible with Class<?>; The issue was visible in TestCross but test cross still succeeded because the assert was not called in junit test runner thread
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.

None yet

2 participants