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

[Ken Finnigan (JIRA)]

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

Ken Finnigan commented on SEAMINTL-7:
-------------------------------------

Am I correct in saying that we are looking to implement the following:

@MessageBundle
public interface BookingStatusMessages
{
   @Message("You are booked to stay at the #{hotel.name} on {1,date}") @StatusMessage(level = INFO, target = "messageWindow", during = TransactionPhase.AFTER_SUCCESS) @Locale("en_US")
   String bookingConfirmed(@MessageParam("hotel")Hotel hotel, Date date);
} 


@MessageParam could also use the variable name by default if no value specified.

As far as I could tell level was not available in @Message, which is why I added it to @StatusMessage.

I have a couple of questions with this:

1) Would it be better to extend @Message to include level, and anything else we think appropriate?  Such as adding a format type of EL?

2) How would we support the text of a message residing in either property files, database or some other resource?

Any thoughts/tips on implementing the above would be appreciated.

I'd also like to support the following, though not necessarily for the Beta:

1) @PluralText/@PluralCount to specify a message content based on a count of a parameter.  Similar to GWT

2) @Key to define the property key as being something other than the method name.  This would come in handy for an application where they already have a lot of properties defined, potentially with short hand names, that they may want to define more descriptively in the method name


> Rewrite Messages API along the lines of JBoss Logging 3
> -------------------------------------------------------
>
>                 Key: SEAMINTL-7
>                 URL: https://issues.jboss.org/browse/SEAMINTL-7
>             Project: Seam International
>          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