HHH-19629 Hibernate Processor may fail when repository method parameter has more than one annotation (e.g. multiple constraints) / HHH-19630 Hibernate Processor may fail if the return type is a single entity and annotatated with multiple annotations

[marko-bekhta]

https://hibernate.atlassian.net/browse/HHH-19629
https://hibernate.atlassian.net/browse/HHH-19630

cc: @cigaly

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

---

[cigaly]

It is working, with that comment that parameter will be annotated with two Nonnull annotations, but this will not cause any error. And if some purist have problems with that, (s)he can fix it.

[cigaly]

And if you really want some nitpicking, maybe you can (in typeAsString) move

result = type.toString();

into else branch (when type is DeclaredType result this is redundant call).
Also, you may consider to use collect( Collectors.joining( ",", "<", ">" ) ) instead of concatenating prefix and suffix in separate statements.
Of course, neither of those changes will make big difference.

[gavinking]

I've been avoiding the use of toString() for this, since the Javadoc doesn't clearly say it's the qualified name, and there are more things than javac.

[gavinking]

What I mean is, I would prefer to see TypeElement.getQualifiedName() here.

It's obnoxious that there is no DeclaredType.getQualifiedName() method, and that DeclaredType.getElement() doesn't return a TypeElement.