Skip to content

[enh] Support overloaded ServiceMethod references#2142

Merged
AxelRICHARD merged 1 commit intomainfrom
ari/enh/serviceMethod
Apr 15, 2026
Merged

[enh] Support overloaded ServiceMethod references#2142
AxelRICHARD merged 1 commit intomainfrom
ari/enh/serviceMethod

Conversation

@AxelRICHARD
Copy link
Copy Markdown
Member

Add overload-safe ServiceMethod factories that accept explicit Java signature types so ambiguous service method references can be resolved.

Also store the resolved Method declaration instead of only the method name, add focused tests for overloaded services, and update the developer documentation with the new API usage.

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@AxelRICHARD AxelRICHARD added this to the 2026.5.0 milestone Apr 15, 2026
@AxelRICHARD AxelRICHARD force-pushed the ari/enh/serviceMethod branch 2 times, most recently from 93ab76d to a01219a Compare April 15, 2026 08:58
Add overload-safe ServiceMethod factories that accept explicit Java
signature types so ambiguous service method references can be resolved.

Also store the resolved Method declaration instead of only the method
name, add focused tests for overloaded services, and update the
developer documentation with the new API usage.

Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the ari/enh/serviceMethod branch from a01219a to 6e66eaa Compare April 15, 2026 08:59
@AxelRICHARD AxelRICHARD merged commit ec82950 into main Apr 15, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the ari/enh/serviceMethod branch April 15, 2026 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant