Here's a random thought: would any other format be better than XML for what is effectively describing CDI annotations? :)
Matt On Mon, Sep 24, 2012 at 12:11 PM, Jason Porter <[email protected]> wrote: > I haven't heard anything for 15 days on this. Seems like it's safe to take > this and put it up on the wiki and get started. > > On Wed, Sep 19, 2012 at 12:17 AM, Romain Manni-Bucau > <[email protected]>wrote: > >> For me that's almost all, wonder about: >> >> 1) xml? Shouldnt we discuss about it when this thread will be done? >> 2) do we want it extensible to let the user add 'shortcuts' (webservices, >> camel context...)? >> Le 19 sept. 2012 00:09, "Jason Porter" <[email protected]> a écrit : >> >> > Let's start listing requirements and use cases for what we want the XML >> > config module to do. I know I have heard of two: >> > >> > 1) Bean configuration and wiring to allow another integration point with >> > CDI for things such as Drools or other projects which may not be directly >> > configured via Java >> > 2) Applying changes to beans such as interceptors to a wide range of >> > classes via a matched regex (Mark, we'll need your use case here) >> > >> > What else do people have? >> > >> > -- >> > 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 >> > >> > > > > -- > 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
