Linda/Bill,
What is the practical possibility we can include this in Java EE 7? If
you are still seriously considering it, I have some time now to put
together a detailed proposal (the time window will not last long). One
important part of an XML configuration revamp would be to load properly
files and system/environment variables from EL (that might be important
to add to EL regardless of this).
Thanks,
Reza
On 6/6/2011 6:01 PM, Linda DeMichiel wrote:
> Antonio,
>
> Sounds interesting, tell us more....
>
> thanks,
>
> -Linda
>
>
> On 6/2/2011 10:47 AM, Antonio Goncalves wrote:
>> I would like to share some thoughts with you.
>>
>> I've used in the past Spring Config and latelly I've attended a
>> conference that talked about Seam Config. Clearly I can
>> see the benefit of having easy configuration on the entire platform.
>> At the moment we have ejb-jar.xml and environment
>> entries to configure our EJBs. We can also use the web.xml to pass
>> some parameters to our servlets and bits and pieces
>> in the application.xml file.
>>
>> Why not having a seperate spec that takes inspiration from Seam
>> Config, Spring Config and so on to be able to configure
>> the entire platform (a CDI bean as well as an EJB...). Configuration
>> will also be used for Paas purposes of course.
>>
>> Configuration is an important topic and developers never know where
>> to put it : property files, XML, database, JNDI. Why
>> not having a spec that specifies how configuration should work (I
>> really like the Seam Config approach) and each spec
>> could then use it to specify how to configure a specific component,
>> as well as batch processing or Paas/Saas
>> configuration...
>>
>> Again, my 2 cents
>>
>> --
>> Antonio Goncalves
>> Software architect and Java Champion
>>
>> Web site <http://www.antoniogoncalves.org> | Twitter
>> <http://twitter.com/agoncal> | Blog
>> <http://feeds.feedburner.com/AntonioGoncalves> | LinkedIn
>> <http://www.linkedin.com/in/agoncal> | Paris JUG
>> <http://www.parisjug.org>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1382 / Virus Database: 1511/3682 - Release Date: 06/05/11
>
>