[AXIS2-3833] WSDL cached/not refreshed when service updated

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: 1.5.6, 1.6.1
• Environment: XP SP2, Apache 2.2, Tomcat 5.5, JDK1.6.0_06
• Assignee: Unassigned
• Reporter: Stephen Kilburn
• Created: 02/Jun/08 16:21
• Updated: 20/Apr/12 02:34
• Resolved: 20/Apr/12 02:34

Description

I compile a service using Ant to an .aar and deploy it (using code modified from the sample WeatherSpringService). Service shows up correctly. Then recompile it adding a new method or change the name of an existing method. When service is redeployed Axis2 listServices still lists the old method name and none of the new methods are shown. When I look at the WSDL it is correct for the old service.

I have confirmed that the new .aar has been deployed correctly, shut down and restarted Tomcat, (tried other variations like shutting down Tomcat, deleting the .aar, starting up Tomcat, then redeploying the .aar), shut down and restarted Apache, and cleared the browser caches. None of this has helped. Shutting down Tomcat, deleting the Axis2 service, and reinstalling the .war fixes this. I have concluded from the system behaviour that Axis2 is caching its generated WSDL for the service somewhere and isn't deciding to do a cache refresh. I have searched everywhere I imagine this information might be stored, but have been unsuccessful in finding it.