Hello,

I am experiencing an issue and wanted to see if anyone else has seen this. 
 When I execute an Axis2 client stub in a standalone Java application (ie 
- similar to the test driver that can be generated using the wsdl2java 
tool),  the deploy() method in the ModuleDeployer class causes copies of 
the different module files from the repository to be written to my 
webserver's temporary directory.  The problem is, these files are never 
cleaned up when the application completes, so everytime I run the 
application I get new copies of the files.  It appears as though nothing 
is ever "undeploying" these modules.  Looking at the undeploy() method in 
the ModuleDeployer class confirms this - the method is empty.

Interestingly, I see the same deployment behavior when I use Axis2 client 
stubs in a web application, except that the files appear to be cleaned up 
by my webserver (not Axis2 code) when I shut down the server.  It appears 
as though the code is assuming that the webserver will clean up these 
files, but that won't work if running as a standalone app.   Is anyone 
else seeing this?

Thanks,
Wally




The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Reply via email to