Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gerhard.petracek@gmail.com
 designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAF9TksMaDH5awv36PyQsuVCu1nJcQv_e3h0FaX1qh2rbKxB26A@mail.gmail.com>
References: <1349457868.27068.YahooMailNeo@web28902.mail.ir2.yahoo.com>
 <CAF9TksMaDH5awv36PyQsuVCu1nJcQv_e3h0FaX1qh2rbKxB26A@mail.gmail.com>
From: Gerhard Petracek <gerhard.petracek@gmail.com>
Date: Fri, 5 Oct 2012 21:18:02 +0200
Message-ID: 
 <CAGJtJfGdPJsWTazdJbZ44n2qhZ1=3L2j4NN5wn34DsuM5qbxrw@mail.gmail.com>
Subject: Re: proposal for JSF Messages
To: deltaspike-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d042f9d6636c37a04cb54bcc9

--f46d042f9d6636c37a04cb54bcc9
Content-Type: text/plain; charset=ISO-8859-1

hi jason,

that's for sure just a first idea.
e.g. we also need the possibility to add messages for a specific component.

regards,
gerhard


2012/10/5 Jason Porter <lightguard.jp@gmail.com>

> On Fri, Oct 5, 2012 at 11:24 AM, Mark Struberg <struberg@yahoo.de> wrote:
>
> > Hi folks!
> >
> > I thought quite some time about how we could do the typesafe messging for
> > JSF. Today I had the following idea.
> >
> >
> > Imagine a typesafe message
> >
> > @MessageBundle
> > public interface SimpleMessage
> > {
> >     @MessageTemplate("Welcome to %s")
> >     Message welcomeTo(String name);
> > }
> >
> > This is nice but it's hard to use it for creating FacesMessages that way.
> >
> > Now imagine the following
> >
> > @Inject
> > JsfMessage<SimpleMessge> message;
> >
> > ...
> >
> > message.addInfo().welcomeTo("DeltaSpike);
> >
> >
> >
> > public interface JsfMessage<T> {
> >   T addInfo();
> >   T addWarning();
> >   T addError();
> >   void clear();
> > }
> >
> >
> > I think it is possible to implement this, right?
> >
> > Wdyt from a users perspective?
> >
> > LieGrue,
> > strub
> >
> >
> This looks like a great start. In IRC we discovered we need to determine if
> the text goes to the summary or detail. We already have the severity with
> the methods. I'd suggest having each of those methods take an enum (DETAIL,
> SUMMARY, BOTH or similar). One drawback I see about this is you can't
> define a different message for the detail and the summary on one line, but
> that may not be the end of the world.
>
> --
> Jason Porter
> http://lightguard-jp.blogspot.com
> http://twitter.com/lightguardjp
>
> Software Engineer
> Open Source Advocate
> Author of Seam Catch - Next Generation Java Exception Handling
>
> PGP key id: 926CCFF5
> PGP key available at: keyserver.net, pgp.mit.edu
>

--f46d042f9d6636c37a04cb54bcc9--