I have an EJB jar file which gets deployed to several different machines, and each machine needs different 'tweaks' to the settings of the EJB. At the moment I am using <env-entry> tags in the ejb-jar.xml file to configure the application.
The problem is that the system administrator must explode the jar for each computer, modify the environment variables, re-compress the jar, then copy it and deploy it.
This is silly in my opinion. There must be a way so that he can configure these environment variables external to the jar file?
Or alternatively, I can read them using some other method - perhaps another JNDI location.
What this boils down to is...
How can we easily configure an EJB jar without exploding it?