[jboss-jira] [JBoss JIRA] (LOGTOOL-144) Make JBoss logging annotations accessible at runtime
Francois JACQUES (Jira)
issues at jboss.org
Fri Jan 3 11:38:30 EST 2020
[ https://issues.redhat.com/browse/LOGTOOL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941132#comment-13941132 ]
Francois JACQUES commented on LOGTOOL-144:
------------------------------------------
In our specific use case we are looking for the generated message code : prefix-padding-code.
Indeed, the information, while still being in the class file, is not read and stored in the JVM memory. Now it's still possible to read this information using a bytecode reader at runtime. But it seems more fragile and overkill for the use case.
> Make JBoss logging annotations accessible at runtime
> ----------------------------------------------------
>
> Key: LOGTOOL-144
> URL: https://issues.redhat.com/browse/LOGTOOL-144
> Project: Log Tool
> Issue Type: Enhancement
> Reporter: Francois JACQUES
> Priority: Major
>
> Hi,
> We have a use case where we are creating a Java proxy to access meta information of a logger. In this scenario we need to access the `@Message` and `@MessageLogger` annotations at runtime. This is not possible as there retention policy is set to `@Retention(CLASS)`.
> Do you see any problem/value into changing the retention policy to runtime for all annotations in JBoss logging ?
> Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list