java-annotations | Annotations for JVM-based languages | Runtime Evironment library

I have the following Java class:

It's just not working. I saw the docs at

https://docs.spring.io/spring-boot/docs/1.5.19.RELEASE/reference/htmlsingle/#boot-features-external-config

I saw the answers at

Spring boot externalize config properties/messages on Java annotations

I have

I'm currently learning about Android annotation topic. I have read this "A retention policy determines at what point annotation should be discarded." My question is why do Java need to discard an annotation at some point? or for what purpose?

ref: https://www.java2novice.com/java-annotations/retention-policy

When i add a new properties file to my project inside resources and name it as for example "lang1" than the BUNDLE_NAME is recognized correctly.

But if i add an ResourceBundle containing lang2_de and lang2_en and try to use its base name as BUNDLE_NAME it shows me the following error "Invalid resource bundle reference 'lang2'.

So i basically have 3 files.

1. lang1_de.properties
2. lang2_de.properties
3. lang2_en.properties

lang2 is bundled into an Resource Bundle with "'base name' = lang2"

This is working with kotlin:

Class MyClass has a numeric field number with annotations.

I am trying to write a scanner for custom annotations based on the answer in Scanning Java annotations at runtime.

However, to speed up the process, I only want to scan the classes under the main package (package which has the main class and its sub-packages). Figured that the easiest way to determine the package name would be from the main class.

The code I am writing would end up in a library which will be used by Spring Boot applications. So I have no way of knowing the name of the main class. Is there a way to determine the name of the main class at runtime in Spring Boot application?

Regards,

Anoop

I'm writing annotation processor, and I need to check if particular TypeMirror implements specific interface. The question Java Annotations Processor: Check if TypeMirror implements specific interface provides an answer for non-generic interfaces. But it doesn't work for generic interfaces, for example String is implementing Comparable - and the code using isAssignable doesn't work.

This code works as expected:

I am trying to run our Spring-MVC application which has Cometd(3.0.9) on Jetty 9.2. Currently it's working perfectly with Tomcat7, but we are checking out Jetty as another application container for some other requirements. However, Cometd won't start, and throws a 500. Here is the only error we get in backend again and again :

I am trying to create a recursive schema using GraphQL Java Annotations, but throws an exception.