> Yes, but it may be possible that the ClassLoader (for > whatever reason) has a cached version of the older class and > it is not loading the new class when the web app reloads. > Have you tried rebooting the application server on the > development machine? If the problem still occurs on the dev. > box after the application server reboots then you could rule > out the ClassLoader issue. It may be a pain in the ***, but > it would eliminate a path.
To try to eliminate anything connected with this, I changed the name of the class in question from "SeasAdjData" to "SeasAdjBean". No change in behavior. It works flawlessly on my local server, but I get the same message on the dev server. (With "SeasAdjData" changed to "SeasAdjBean", of course. -- Tim Slattery [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
