quarkusio/quarkus

Make the RegisterForReflection annotation more flexible for Native

Open

#3,883 opened on Sep 5, 2019

View on GitHub
 (19 comments) (0 reactions) (0 assignees)Java (12,967 stars) (2,464 forks)batch import
area/native-imagegood first issuekind/enhancement

Description

Description Would be nice have a way to tell to @RegisterForReflection annotation what I want instead of using the reflection-config.json file as stated here https://quarkus.io/guides/writing-native-applications-tips.

Currently, If I want only public methods to use reflection, I need to create the file below:

reflection-config.json:

[
  {
    "name" : "something.test.resource",
    "allPublicMethods" : true
  }
]

Implementation ideas: @RegisterForReflection(allPublicMethods=true)

Contributor guide

Tech stack
java
Domain
backendtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java annotationsReflection in native imagesQuarkus build system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue requests adding attributes to the @RegisterForReflection annotation (e.g., allPublicMethods, allDeclaredMethods, allDeclaredConstructors) to avoid using reflection config.json. Investigate the current implementation of @RegisterForReflection in the Quarkus codebase (likely in core/deployment or similar). Look at the annotation definition and the corresponding processor that generates reflection configuration. Add new optional attributes to the annotation and update the processor to handle them. Ensure backward compatibility. Alternatively, check comments for any suggested approaches from the community.
Make the RegisterForReflection annotation more flexible for Native · quarkusio/quarkus#3883 | Good First Issue