hi nik, right now it's a reduced api (including some changes we need to be compatible with the type-safe message approach). i haven't committed the payload, (parameter-)formatter, message-handler, localizable,... approach.
@ converter: we already have a ConverterFactory in deltaspike (a first draft) -> imo we should try to reuse it. yes the message-severity is one possible payload in codi. (after we finished part #1-#4 we should review the result once again.) regards, gerhard 2012/4/20 Nicklas Karlsson <[email protected]> > Message severity and additional stuff are Payloads? > > On Fri, Apr 20, 2012 at 8:15 AM, Nicklas Karlsson <[email protected] > >wrote: > > > The basic API looks fine so far (similar to CODI?) > > > > About the parameter formatting, are you planning some Map<Serializable, > > Converter> registry that you could use for Number/Date formattings? Or > does > > the message interpolator work on String.format by default. Or something > > else? > > > > > > On Thu, Apr 19, 2012 at 2:38 PM, Gerhard Petracek < > > [email protected]> wrote: > > > >> hi nik, > >> > >> i updated [1] -> imo we should just finish part #1 and the documentation > >> for it (at [2]). > >> furthermore, we have to fix our test-setup for integration tests. > >> > >> regards, > >> gerhard > >> > >> [1] > >> > >> > https://cwiki.apache.org/confluence/display/DeltaSpike/Message+Module+Drafts > >> > >> [2] > >> > >> > https://cwiki.apache.org/confluence/display/DeltaSpike/Temporary+Documentation > >> > >> > >> > >> 2012/4/19 Nicklas Karlsson <[email protected]> > >> > >> > Ping, > >> > > >> > What is the status of the Messaging module? The wiki has a minimal > >> basic > >> > API and DELTASPIKE-119 has a wishlist. What's the next step? > >> > > >> > --- > >> > Nik > >> > > >> > > > > > > > > -- > > --- > > Nik > > > > > > -- > --- > Nik >
