Let me explain a few things about the format I suggested... It's extensible because TomEE authors can add new configuration classes to the classpath in the future. this is better than XML and Properties. With an XML format, we're "locked in" to a particular XSD and isn't extensible. Properties are extensible fortunately.
It's typesafe because it'll be hard to make mistakes: the compiler will catch them. XML is typesafe with an XSD. Properties is not typesafe, the only way to check it is to run it or manually compare it against the documentation. I included configuration environment IDs: @ConfigurationId(env = "Development") My hope is the TomEE console could maybe say, "choose a configuration name" when you deploy the ear. I also hope this could be put on the server classpath somewhere, like in tomcat/lib. That way you could deploy the ear once, then later an administrator could redploy the configuration independently. -- View this message in context: http://openejb.979440.n4.nabble.com/DISCUSS-New-descriptor-format-tp4657040p4657088.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
