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

Resteasy: do not use Jandex's ClassInfo in a Set #8687

Merged
merged 1 commit into from
Apr 22, 2020

Conversation

aloubyansky
Copy link
Member

since it implements neither equals() nor hashCode()

Comment on lines +238 to +242
String className = clazz.name().toString();
if (!additionalPaths.contains(annotation)) { // scanned resources only contains real JAX-RS resources
scannedResources.putIfAbsent(clazz.name(), clazz);
}
reflectiveClass.produce(new ReflectiveClassBuildItem(true, true, className));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't these be outside of the if (!withoutDefaultCtor.containsKey(clazz.name())) check?

Copy link
Member Author

@aloubyansky aloubyansky Apr 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's in withoutDefaultCtor it's already been processed, hasn't it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is certainly true, but the point of withoutDefaultCtor wasn't really to guard against that case.
I do understand what your checking here, it just seems odd to reuse withoutDefaultCtor to perform this check.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could introduce another Set for that purpose.

@geoand
Copy link
Contributor

geoand commented Apr 22, 2020

Let's get this one in for now

@geoand geoand merged commit 9468248 into quarkusio:master Apr 22, 2020
@gsmet gsmet added this to the 1.4.0.Final milestone Apr 22, 2020
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.

3 participants