Hey Romain, Looks awesome! I was playing around with it earlier. Noticed also you added the daemons section in the code which is a must imo. I blogged about my original idea for the openejb.json here, http://chrischristo7.tumblr.com/post/52453371878/idea-for-an-elegant-configuration-of-tomee-openejb.
Its not to dissimilar to the one you've been developing. Although you explicitly put container/resource properties in its own "properties" json key. I think its cleaner without, but after looking at the code I realised why you did it that way (easier to map to existing SaxOpenejb etc). Although whatever that can be done to make it as simple as possible the better really. A simple and elegant configuration for a server goes a long way these days. So many problems arise for not knowing how to configure things, and its not because of a lack of documentation, its usually because its just too messy/complicated too many config files etc. I've just gone through the whole process of learning how to setup OpenEJB so I know the pain! For this reason, I would love to contribute to a page dedicated to this json configuration. It could be a nice way to introduce newbies to configuring TomEE/OpenEJB in a simple one stop shop, rather than getting knees deep into all the existing config files. How could I go about doing this? Chris Christo --- Twitter: https://twitter.com/ChrisChristo7 Tumblr: http://chrischristo7.tumblr.com LinkedIn: http://uk.linkedin.com/in/chrischristo GitHub: https://github.com/ChrisChristo On 10 Jun 2013, at 14:08, Thiago Veronezi <thi...@veronezi.org> wrote: > I like it! > I will give it a try this evening. > > Thanks, > Thiago. > > > > On Mon, Jun 10, 2013 at 3:02 AM, Romain Manni-Bucau > <rmannibu...@gmail.com>wrote: > >> Worked a bit on it >> >> tomee.json supportes basically what is in tomee.xml with the convention >> there is a root pluralized and a child with an id (no need to repeat root >> name even at the singular form: >> >> http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/test/resources/openejb.json >> ) >> >> comments are supported through "__" key. >> >> i added the support for resources.json based on our resources.xml model >> too. >> >> *Romain Manni-Bucau* >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >> *Blog: **http://rmannibucau.wordpress.com/*< >> http://rmannibucau.wordpress.com/> >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >> *Github: https://github.com/rmannibucau* >> >> >> >> 2013/6/7 Romain Manni-Bucau <rmannibu...@gmail.com> >> >>> Hi guys, >>> >>> just started a work on a json config instead of our xml/properties one. >>> >>> Here is the idea >>> >> http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/test/resources/openejb.json(not >>> fully implemented - only resources should work) >>> >>> I first thought being able to remove properties wrapping but we need it >> to >>> know if that's attributes of the resource or config (type, class-name, >>> provider...) >>> >>> In the impl i used rhino which is in the jvm since 1.7 and for previous >>> version you need to add a javascript impl of the JSR 223 (not blocking >> IMO >>> since 1.6 is decreasing) >>> >>> The impl doesn't use an optimized version of code but it reuse the xml >>> parsing so we keep something consistent between both configs. >>> >>> >>> wdyt? >>> >>> *Romain Manni-Bucau* >>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >>> *Blog: **http://rmannibucau.wordpress.com/*< >> http://rmannibucau.wordpress.com/> >>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >>> *Github: https://github.com/rmannibucau* >>> >>> >>
