[seam-issues] [JBoss JIRA] Commented: (SEAMINTL-7) Rewrite Messages API along the lines of JBoss Logging 3

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/browse/SEAMINTL-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566659#comment-12566659 ] 

Dan Allen commented on SEAMINTL-7:
----------------------------------

I talked to David Llyod while in Antwerp about:

1. reusing the @Message annotation
2. adding the EL functionality
3. moving @Message to the org.jboss.i18n package

He was firm about keeping JBoss Logging as simple as possible. He suggested that we create our own, simplified annotations rather than trying to reuse the annotations from JBoss Logging.

Plus, one annotation is a much simpler API than two from the user's perspective. So I'm in favor of either @StatusMessage or @ReportStatusMessage. I'm not sure if "Log" in @LogMessage is meant to be read as an action (verb) or not. If it is, then that's what @ReportStatusMessage is meant to parallel.

> Rewrite Messages API along the lines of JBoss Logging 3
> -------------------------------------------------------
>
>                 Key: SEAMINTL-7
>                 URL: https://jira.jboss.org/browse/SEAMINTL-7
>             Project: Seam i18n
>          Issue Type: Feature Request
>          Components: Messages
>    Affects Versions: 3.0.0.Alpha1
>            Reporter: Ken Finnigan
>            Assignee: Pete Muir
>             Fix For: 3.0.0.Beta1
>
>
> Rewrite messages API along the lines of JBoss Logging 3 to be consistent with the logging approach once the switch from slf4j is made to JBoss Logging 3.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira