[jboss-jira] [JBoss JIRA] (LOGTOOL-144) Make JBoss logging annotations accessible at runtime

James Perkins (Jira) issues at jboss.org
Fri Jan 3 11:46:19 EST 2020


    [ https://issues.redhat.com/browse/LOGTOOL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941139#comment-13941139 ] 

James Perkins commented on LOGTOOL-144:
---------------------------------------

We use the bytecode to generate our pages with all the messages for Wildscribe, https://wildscribe.github.io/WildFly/18.0/log-message-reference.html. 

I definitely have concerns with the extra metaspace that is likely required. This could be a problem for cloud environments where memory is a concern.

> 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