Ok, Anyone ever have this problem ? My company has WL 6.1 sp3 running on a SOlaris two machine cluster. Whenever I add a new method that is exposed by a webservice, the new methods do not show up in the WSDL doc. To make sur enothing was cached anywhere, I used the WL console to stop both servers. We STILL saw the webservice as available even thought both sides of the cluster were shit down. This led us to believe there was some type of caching going on someplace. Our admin stoppped and restarted the cluster service, and we STILL saw the wsdl doc !!! Anyway . . . the only way we could get the WSDL to show the correct output was to reboot the machines themselves. This is not ideal as we don't want to be starting and stopping machines since there are other applications running besides mine. If anyone has had any experience with this phenonmenon please share with the class! Thanks in advance - Mike
'Some people have a way with words. Other people . . . not have a way I guess.' - Steve Martin
Our admin stoppped and restarted the cluster service, and we STILL saw the wsdl doc !!! Are you sure it wasn't your browser that was caching the old page? Most modern browsers tend to be very aggressive with their cache management and these problems can arise. Most of the time when something strange like this happens, I do a Ctrl-F5 to force a refresh and that solves the problem. Of course, this is complete speculation on my part because I have not experienced your problem with WLS Web Services.
Joined: Feb 26, 2002
I should have mentioned that I did clear my browser cache. I even went to a second PC that had never even navigated to the webservice URL. It too showed up ! This is a strange one I admit.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com