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

Dan Allen (JIRA) jira-events at lists.jboss.org
Tue Nov 9 23:48:01 EST 2010


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

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

There's a forth option. We can provide a built-in interface that automatically applies the qualifier:

public interface Targetable<T>
{
   T target(String target);
}

@StatusReporter
public interface RegistrationStatusReporter extends Targetable<RegistrationStatusReporter>
{
   @Message(level = WARN, value = "Username taken!") @ReportStatus
   void duplicateUsername(String username);
}

status.target(clientId).duplicateUsername(username);

> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list