-- Werner Keil 590 Madison Avenue. New York. NY 10022 | 68 Lombard Street. London EC3V 9LJ UK US Toll Free: +1-877.964.1981 | Worldwide Toll Free: +800.225.53482 Twitter @wernerkeil | Skype: werner.keil | www.emergn.com | Reshaping IT * Java 7 Launch: July 17 2011, Bangalore, India. Werner Keil, Executive Committee Member (SE/EE), will represent "Java Community Process" On Wed, Jul 13, 2011 at 12:33 AM, Reza Rahman <reza_rahman_at_lycos.com> wrote: > Bill, > > In that case, I think the existing documentation for CanDI configuration > suffices: http://caucho.com/resin-4.0/**admin/config-candi.xtp<http://caucho.com/resin-4.0/admin/config-candi.xtp> > . > > Basically the key concepts we would like to see (strictly in order of > priority) are: > * Compact, "Java-like" schema-based syntax, similar to the Seam Config > module/CanDI XML. > * Being able to configure CDI and EJB using this syntax. > * Being able to load property file values/environment property values > through EL (this might be a good enhancement to EL regardless of this). We > allude to this in the docs, but it is not completely hashed out. > * Being able to configure all Java EE managed beans including Servlets > using this syntax. Like Resin configuration we would actually prefer that > most Java EE configuration looks like managed bean configuration using XML. > * Have separate schemas for current XML DD values that do not match the > managed beans/annotation paradigm well. Taking the web.xml as an example, > things like module names, session configuration, etc can go in such schemas. > I think the number of tags that genuinely fall in this category is quite > small. > * Being able to configure multiple things in any Java EE XML DD using > schemas. For example, you would be able to configure CDI beans in web.xml if > you want. > * Let all Java EE XML DDs have capabilities similar to web.xml fragments. > > Let me know if any of this requires further details. Since we started down > this path, I'd prefer to follow this to the end. I do think there is > tangible befits for developers in such an enhancement and at least some of > it is doable in Java EE 7 if there is a desire to do it. We in the Resin > team can see if we have the resources to contribute to this significantly if > resources are an issue (I do feel a little funny soliciting Oracle with an > offer of additional resources from a tiny company like Caucho :-)). > > Cheers, > Reza > > > > On 7/11/2011 2:44 PM, Bill Shannon wrote: > >> I think at this point we just need to understand more to assess whether >> this would be feasible in the limited time we have. Maybe a brief >> informal description with examples would be better than a detailed >> proposal >> at this stage? >> >> Reza Rahman wrote on 07/11/11 08:26 AM: >> >>> 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<http://www.antoniogoncalves.org>> >>>>> | Twitter >>>>> <http://twitter.com/agoncal> | Blog >>>>> <http://feeds.feedburner.com/**AntonioGoncalves<http://feeds.feedburner.com/AntonioGoncalves>> >>>>> | LinkedIn >>>>> <http://www.linkedin.com/in/**agoncal<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 >>>> >>>> >>>> >>> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 10.0.1388 / Virus Database: 1516/3758 - Release Date: 07/11/11 >> >> >> > >
(image/gif attachment: 347.gif)