You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Mark Bloore <mb...@fmco.com> on 2001/03/08 22:01:06 UTC
reloading a component during development
i am using soap 1.2 and tomcat 3.2.1.
i am trying to create a simple soap java object of my own, using a soap
example as a base, and find that when i modify the object and deploy it,
what runs is the object that i first deployed under that same ID. oddly, i
can change the class name in the deployment descriptor file to something
that does not exist, and my client still runs fine! yet if i change the
method names there, i get an error.
clearly my class file is getting cached somewhere, but i can't figure out
where. the context for my work is in tomcat's server.xml, and set to be
reloadable, but it does not reload. (i'm not sure that that would have an
effect on soap anyway.) my development directory has a WEB-INF subdirector
with a (minimal) web.xml file. restarting tomcat clears this cache.
can anyone tell me if i've missed a step?
--
mARK bLOORE <mb...@fmco.com>