On Aug 23, 2012, at 3:37 PM, exabrial wrote: > A couple of things... > > What about a typesafe Java Configuration descriptor? Would it be possible to > use both a compiled class and a .java file? I don't think either of these > have been tried on a ApplicationServer (yet!)
We actually have (close to) that already, just not exposed. - http://openejb.apache.org/dev/configuration-and-assembly.html Our @ApplicationComposer API allows you to build up the app in code. I've sometimes wondered if people might like to actually deploy like that. You can certainly do that with an embedded server, but could be useful for a "regular" server. Having a class that we execute for creating the application would be a fairly easy thing to add. Did you want to give it a try? Could be a fun experiment with an nice way to get started hacking. > If OpenEJB/TomEE stays XML, I would greatly prefer to have an XSD that has > all possible attributes and options built into it. This sounds old > fashioned, but hitting cntrl-space in Eclipse while editing an XML file > makes configuration a snap. It makes for less trips back to the > online-documentation and mailing list too :) That's good feedback. It means no properties, but that might be overall better. We could still use properties internally, but in terms of the xml it definitely changes things. > The only thing I'm picky about is having "one way" of specifying the data. > Having multiple ways to specify the same thing will likely confuse > newcowers: > > <Configuration> > <AsynchronousPool> > CorePoolSize = 10 > > <Configuration> > AsynchronousPool.CorePoolSize = 10 > > My .02! Thanks, this definitely crossed my mind and thought "this could be bad too". It's good to hear input. The more the better. We'll have to live with the result for several years, so getting this right is key. -David
