You'll have to be more specific on what you need. Most of the parameters should be outside the code already, so you may have application settings that you want to externalize?
For example, my app saves files uploaded by the user. This system will be installed in several servers to be used localy, so the folder where files will be saved will vary from server to server.
I'd like to put this information (where to store files) in an external configuration file, and not inside the EAR file.
You can have this information in the database.
May be you should take a look at Chapter 4. Configuring Seam components in jboss-seam-2.0.0.BETA1\doc\reference\en\pdf\seam_reference.pdf
Your best choices would be either database or jndi if you don't want it in the ear file / hierarchy.
I would use jndi if your sysadmin is configuring the file location as it is easier for them to change the files that store the jndi settings than it would be to update a database.
If you go for database, you can get the server's host name and use that as a filter in case all the app servers are going to the same db.
I think that the DB option is the easiest by now.
I think JNDI would be the best of the worlds, but I'm a newbie in JNDI and configuration in JBOSS.
Do you recommend any article or a good JNDI tutorial with a JBOSS or JEE enphasis?
btw... Thanks you all for the quick answer.