Keeping properties file out of war

[angelodel80]

We've got a Seam app doing all the usual things with datasources. Notably, pulling datasource info (url, username, password, etc.) from a separate property file.

Is there a way to store and source .properties file outside of the .war? If I've got this right, Seam assumes the root of the paths used  are the root of the .war?

But that's a bummer since installing on a new server (with a different database) means have to explode the .war just to edit the datasource-config file.

How do you guys handle this situation? Or do you just live with having to explode the .war to make config edits?

Thanks!

Angelo Mario

[cosmo]

If you created your Seam project from seam-gen it already comes with a nice Ant script that support different profiles. Are you taking full adavantage of it?

[angelodel80]

Thanks Aldo!

You are Italian, right? Me too!

Yes, I know the ant solution. But the problem is different: I have to read several properties in real-time after the deploy has been made , such as the datasource environment, without explode my war file! So  properties should be written in a file out of war. In this way the war keeps the same and the changes affect only the .properties file.

I read a lot of posts and documents, but nothing I found for my particular matter...

[babazs]

1. use JBoss persistent mbeans

2. use the JBoss property service:

You can add attributes to Jboss5/server/default/deploy/properties-service.xml, then, you can read this from a Seam component. You also have a possibility to create multiple property file.
http://community.jboss.org/wiki/PropertiesService

[daniele4]

You can create a system property where you define the path of your properties file. You can do that adding this vm arguments: -Dpropertyname=path. Then you can read the value of property from java code by System.getProperty("propertyname");

[angelodel80]

Thanks a lot!

I will try it...