Another option were to put properties into geronimo-application.xml or openejb-jar.xml where they would mirror the values in ejb-jar.xml/env-entry, the same ways as properties in geronimo-ra.xml override properties in ra.xml. Is think this isn't possible right now, is it?
geronimo-application.xml is often not in the ear, so operations could get the ears from development and keep geronimo-application.xml themselves. I don't know where Geronimo puts the deployment plans after deployment (or is it below var/config ?), probably operations would like if the deployment plans were at a defined location. Juergen -- View this message in context: http://www.nabble.com/Where-to-store-secret-EJB-properties--tp20094408s134p20105057.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
