I'd suggest opening both wsdl4j JARs in something like Winzip and verifying which class files are newer (assuming you picked up binary versions of WSDL4j.jar and didn't build them yourself). I think AXIS' wsdl4j.jar was from last June or something like that, as we had an issue where we were using one a couple months later than AXIS was in order to pick up some WSDL4j fixes for our own purposes.
Using the latest one should satisfy both sides as there don't appear to have been incompatible changes with successive WSDL4J builds... -----Original Message----- From: Millard, Ray [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 31, 2002 10:31 AM To: '[EMAIL PROTECTED]' Subject: Axis and CICS Transaction Gateway Has anyone used AXIS and CICS Transaction Gateway from WebSphere Studio Integration Edition 4.1.1? Both require the WSDL4J.jar file. When using both, Axis does not generate the WSDL file when accessing the service with the ?wsdl parameter, for example "http://localhost/axis/services/MyService?wsdl"; I am assuming that they have the same class and AXIS has a newer version than WebSphere Studio. This is what is sent back to the browser: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type></HEAD> <BODY><XMP></XMP></BODY></HTML> Any help or pointers would be greatly appreciated. Thanks!
