All,
I have been using displaytag recently, and found it to be a great tool. Thanks to all the developers, and everyone on this list.
A question for you, however:
When trying to use decorators and i18n support, I run into hideous problems anytime I recompile my EAR / WAR and redeploy. I can get decorators to work, but when I make a change and redeploy, the appserver gives me a ClassCast Exception. In other words, it seems to me there is some problem with displaytag's classloading scheme, whereby references to old decorators (and other classes relating to i18n support) remain, and when displaytag tries to reference them after the redeploy, those references point to classes that have been invalidated by the new deployment.
Forgive me if this doesn't make sense, and I will be happy to explain it more clearly.
But I wanted to see if anyone else has notcied this problem.
By the way, I also notice a similar problem with changing the displaytag.properties file. I have this file located in my /WEB-INF/classes directory, as suggested. However, the only way I can force displaytag to 'see' any changed properties on redeploy is to bring down the server.
Again, this seems to be a case of displaytag holding not re-reading the properties file after deploy. I believe these two problems are related.
Can someone help?
Thanks!
Josh Meckler
-----------
The information contained in this e-mail message, and any attachment, is confidential and for use solely by the intended recipient. If you have received this message in error, please delete this message immediately. Although Moody's KMV makes every effort to protect its computing environment from malicious code, Moody's KMV is not responsible for any virus or other type of suspect code that may be transferred via this e-mail message.
