ppkarwasz commented on issue #3871: URL: https://github.com/apache/logging-log4j2/issues/3871#issuecomment-3643577614
Hi @anuragagarwal561994 and @snicoll, I finally had time to investigate the issue. The root cause is that `GraalVmProcessor` currently generates **canonical** type names for method parameters (e.g. `org.apache.logging.log4j.core.Filter.Result`), while GraalVM expects **binary names** (e.g. `org.apache.logging.log4j.core.Filter$Result`): essentially the values returned by `Class.getName()`. For array types, GraalVM accepts both `Class.getName()`-style descriptors and the `<element_type>[]` form. The issue is addressed in #3996 and will ship in the upcoming `2.25.3` release. I’ll also open a PR against the GraalVM docs to make the expected type-name formats explicit. -- 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]
