Musachy Barroso wrote:
did you figure it out?
I did find that glassfish was applying my logging levels in a dumb order, resulting in me not seeing logs I thought I was seeing... ...and I did subsequently see an appropriate log message on touching a .class file... ...but I've not since had an occasion where a code update I needed to test included only action class changes, so this trick rather than a redeploy hasn't yet been a viable testing strategy for me, and I've not yet fully tested it. I'll let you know once I see it work.
-Dale --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org