Why some deployed classes seem to persist after rebooting?

I'm just trying out doing some simple tag, i.e. I have

- myTag.java (tag handler class)

- tags-taglib.tld (tag library descriptor)

- myPage.jsp (a simple JSP containing myTag)

I set package to "myPack.tags" inside myTag.java,

compiled it (it produced myTag.class in c:\apache tomcat 4.0\classes\myPack\tags),

and myPage.jsp ran correctly.

Now, I changed the package to simply "myPack" inside myTag.java.

compiled it (it produced myTag.class in c:\apache tomcat 4.0\classes\myPack),

modified tags-taglib.tld accordingly, but now I couldn't get the JSP to

run correctly, and from the error message it looked like Tomcat was trying

to find the class using the old path ("....\myPack\tags"), which I deleted.

I rebooted my PC and it still tried to find the class using the old path.

I figured out that there is some config stuff somewhere that didn't get updated

(for whatever reason) but I have no clue.

Please help, what should I do?

Thanks!

[1045 byte] By [iwjahja] at [2007-9-19]
# 1
I have the same problem, are there any answers yet?Carsten
hfrezkhurefa at 2007-7-8 > top of java,Enterprise & Remote Computing,Web Tier APIs...
# 2
I've found the solution:It's not enough to replace the classes and the tld, it'salso necessary to replace the jsp document or at leastchange the date of it.
hfrezkhurefa at 2007-7-8 > top of java,Enterprise & Remote Computing,Web Tier APIs...