>>I'm sorry but I think that for devs it would be good (think about @DatasourceDefinition / CDI alternatives...) >>But for "production" it will never be used administrators do not compile java code >>IT security policies will never allow to let passwords and other top-secret info to be hard coded in java files
What about a generated config file under a folder like "tomee_conf_files"? During startup or deployment, Tomee would generate the configuration files for all the "TomEEModuleConfiguration" it founds. At the end, we would have a structure like: ..\apache-tomee-plus-1.0.0\tomee_conf_files ..\apache-tomee-plus-1.0.0\tomee_conf_files\app_A_conf.xml ..\apache-tomee-plus-1.0.0\tomee_conf_files\app_B_conf.xml ..\apache-tomee-plus-1.0.0\tomee_conf_files\app_C_conf.xml ..\apache-tomee-plus-1.0.0\tomee_conf_files\app_D_conf.xml The configuration files would be like what the guys proposed before, and they would have the default "production" values defined by the developer. We could also create a maven plugin that generates these files for us during the project build process. It would create war files like... app_A.war |-- images/ |-- index.html |-- jsps/ |-- WEB-INF/ |-- app_A_conf.xml This way we wouldn't impact the server deployment performance. []s, Thiago.
