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 rmannibucau@gmail.com
 designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAF9TksPMO3q7zkiZjLnctyY5MyiLz13ysEAhniRnXNf6ayRnmg@mail.gmail.com>
References: 
 <CAF9TksPMO3q7zkiZjLnctyY5MyiLz13ysEAhniRnXNf6ayRnmg@mail.gmail.com>
Date: Wed, 19 Sep 2012 08:17:05 +0200
Message-ID: 
 <CACLE=7Mw+4_QdqMSXYmKWrnt1TyU4cYbAgPqbVEAy+pz3LWufQ@mail.gmail.com>
Subject: Re: XML Config requirements
From: Romain Manni-Bucau <rmannibucau@gmail.com>
To: deltaspike-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d04083d7fb5aacd04ca07f4c0

--f46d04083d7fb5aacd04ca07f4c0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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" <lightguard.jp@gmail.com> a =E9crit =
:

> 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
>

--f46d04083d7fb5aacd04ca07f4c0--