Hi All, I'm moving my Axis 1.0 deployment over to WebLogic 6.1sp3 from Tomcat. Everything is working fine from Tomcat but my move to WebLogic is proving to be problematic.
I've done some searching on the mailing list and realize there maybe problems with deploying axis in a .war file with beta3. Is this still the case in release 1.0? That is exactly how I'm trying to deploy it. >From what I gather in the mailing list, the problem is that Axis can not find the server-config.wsdd file since it's in a .war file. Did I capture this problem correctly? Are there other problems? I know there was some talk about WebLogic verifying the manifest of the .jar files but that's supposed to be fixed in sp3. If that's the only problem, then I'm seeing something very strange. When I use the browser to point to the URL that would start the Axis servlet. It serves up the familiar "And now...Some Services" web page. On this page, it actually lists the webservice I configured, including the methods that I've defined. This seems to indicate that axis has found the server-config.wsdd file and knows there's different services to be loaded. However, when I use my client to send a soap message to the url, I get back an error 404. I did not change anything between using the browser and using my client. What can be wrong? Is my assumption from the "And now...Some Services" page that axis was able to find the server-config.wsdd file incorrect? If it is, then how did it know the specific web service that my server provides? Is there a workaround now for the deploying axis as a war file problem? Thanks very much in advance for any help you can give me. --Alex
