JinyuChen97 commented on PR #8505:
URL: https://github.com/apache/camel-quarkus/pull/8505#issuecomment-4214635872
> Don't we have more to cover like in `MllpRoutes.java` where we have
`@RegisterForReflection(targets = MllpInvalidMessageException.class, fields =
false) ` ? If yes, could it make sense to modify the prompt to spot those cases
?
oh yes, you are right, this exception is used by onException(class) pattern,
so it can be removed as well.
I also found other exceptions annotated with @RegisterForReflection, but
they are used by throwException(new xxxexception()) and they are not abled to
be detected by the CamelNativeImageProcessor.
integration-tests/servlet/src/main/java/org/apache/camel/quarkus/component/servlet/CustomException.java
annotation: @RegisterForReflection
usage: throwException(new CustomException())
integration-test-groups/http/netty-http/src/main/java/org/apache/camel/quarkus/component/http/netty/NettyHttpRoutes.java
annotation: @RegisterForReflection(targets = IllegalStateException.class,
serialization = true)
usage: throwException(new IllegalStateException("Forced exception"))
integration-tests-support/messaging/common/src/main/java/org/apache/camel/quarkus/component/messaging/it/MessagingCommonRoutes.java
annotation: @RegisterForReflection(targets = IllegalStateException.class,
serialization = true)
usage: throw new IllegalStateException(...)
please suggest if you found more. And should we investigate the solution of
adding throwException(new class) or leave them at the moment?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
