On Thu, Apr 19, 2012 at 6:44 AM, S Ahmed <[email protected]> wrote: > The problem I was having was, when on the production server, I had a > properties file in my /resources folder, and I modified in on the server > but noticed it was still returning the old values. > > I then realized that the class loader was loading the file from the .jar > itself, and not reading from the file (even though the file was updated to > reflect production settings).
Read up on classpath resolution rules. Your file in the *.jar is trumping the one in the directory. The other sin to commit is including a log4j settings file in your jar. :) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
