[
https://issues.apache.org/jira/browse/DELTASPIKE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477813#comment-13477813
]
Gerhard Petracek edited comment on DELTASPIKE-278 at 10/17/12 12:30 PM:
------------------------------------------------------------------------
i still think that we should stick with the type-safe message-payload (=
generic meta-data) we have in codi. in the simple case it's just a marker which
marks a msg e.g. as jsf-msg -> you can use the official jsf-conventions for the
lookup. at the same time you get an advanced concept which allows to
store/forward/... messages with any custom meta-data.
was (Author: gpetracek):
i still think that we should stick with the type-safe message-payload (=
generic meta-data) we have in codi. in the simple case it's just a marker which
marks a msg as jsf-msg -> you can use the official jsf-conventions for the
lookup. at the same time you get an advanced concept which allows to
store/forward/... messages with any custom meta-data.
> add 'category' to Message API
> -----------------------------
>
> Key: DELTASPIKE-278
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-278
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.3-incubating
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.4-incubating
>
>
> Sometimes we need different versions of a rendered message. This could be a
> shortText vs a longText for example. Or in JSF it's the summary vs detail
> message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
