Skip to content

Conversation

@zakkak
Copy link
Contributor

@zakkak zakkak commented Aug 19, 2025

Fixes #49413

cc @gsmet

zakkak added 2 commits August 19, 2025 15:22
Add fallback to use root implementor when no matching handleRequest
method is found in the class hierarchy.

Closes quarkusio#49413
.build());
} else {
// Fall back to the root implementor if a matching `handleRequest` is not found in the class hierarchy
ret.add(new AmazonLambdaBuildItem(lambda, cdiName, streamHandler));
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@gsmet it looks like this addition is enough to handle #49413

I explored the option of removing the !method.parameterType(0).name().equals(DotName.createSimple(Object.class.getName())) check above to make it detect the generic handleRequest method in the abstract class and register it but no matter what I tried I keep getting:

2025-08-19 17:44:06,717 ERROR [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread (TEST)) Failed to run lambda (TEST): jakarta.enterprise.inject.UnsatisfiedResolutionException: No bean found for required type [class io.quarkus.amazon.lambda.deployment.testing.LambdaWithHierarchyTest$AbstractRequestHandler] and qualifiers [[]]
	at io.quarkus.arc.impl.InstanceImpl.bean(InstanceImpl.java:288)
	at io.quarkus.arc.impl.InstanceImpl.getInternal(InstanceImpl.java:309)
	at io.quarkus.arc.impl.InstanceImpl.get(InstanceImpl.java:190)
	at io.quarkus.arc.runtime.BeanContainerImpl.beanInstance(BeanContainerImpl.java:28)
	at io.quarkus.amazon.lambda.runtime.AmazonLambdaRecorder$1.processRequest(AmazonLambdaRecorder.java:168)
	at io.quarkus.amazon.lambda.runtime.AbstractLambdaPollLoop$1.run(AbstractLambdaPollLoop.java:142)
	at java.base/java.lang.Thread.run(Thread.java:1583)

@zakkak zakkak marked this pull request as ready for review October 23, 2025 08:28
@quarkus-bot
Copy link

quarkus-bot bot commented Oct 23, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f7b5799.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@geoand geoand merged commit 3a4e42e into quarkusio:main Oct 24, 2025
45 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.30 - main milestone Oct 24, 2025
@zakkak zakkak deleted the 2025-08-19-fix-49413 branch October 29, 2025 17:23
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.

AWS lambda: Unable to find handler class since 3.25.0

2 participants