From: "David Farrell" <[EMAIL PROTECTED]> > When I changed the Constants.java file, i went to my local classes > folder and uploaded every class with the most recent timestamp.
> I looked at all three Constants.java files and all are correct. IMO, that isn't the class that's causing the problem, it's the one with the line that has Constants.SOMETHING in it. I don't know if Eclipse is smart enough to "know" that the class that uses the constant needs to be recompiled. Once a value gets inlined, there's no longer a connection between the two classes. I'm also not sure a search of a binary .class file will always turn up an arbitrary text string. It still feels like something is using the wrong version of a class. Have you totally shut down anything that could have a class loaded? And recompiled *every* class in the project, not just the ones that Eclipse thinks should be recompiled? At this point I would delete every .class file, reboot if at all possible and see if you can reproduce the error. If you're uploading individual .class files, that seems to me to be asking for trouble. Get it working on your development machine, make the changes required to go to production, recompile, make a .war file and deploy everything together. I'd also move this path out to a .properties file so it can be changed without recompiling. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
