Thanks Anna I suspect that what I am experiencing may be a deployment bug as the failures I am seeing when consuming the service locally (that is, Axis client consuming Axis service on the same box) are not at all apparent when I consume a .NET (BizTalk) service derived from the same WSDL. I found this out today. A pleasant surprise!
In one respect I am very relieved (I have a reasonably happy customer and there are none of the feared interoperability issues), but on the other hand I have spent many wasted man-days - at a cost of course to our company - thinking that I had done something wrong or the WSDL was flawed. You live and learn. Patrick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 26 July 2005 16:50 To: [email protected] Subject: RE: WSDL versus ?WSDL Heya, Putting in a few cents, I ended up using the <wsdlFile> tags in my .wsdd because the version of my WSDL produced by ?WSDL wasn't usable. I had imported a schema instead of embedding it directly into the WSDL and the generated version stripped out the schemaLocation attribute - thus rendering an incomplete WSDL that no one could consume. When I asked about it here, the indirect answer was to use <wsdlFile>. I decided it was better to give the user the original WSDL than rely on a generated copy since I couldn't rely on them to match. YMMV. Anna Anna Veirauchs .Software Engineer . SunGard . Wealth Management Services . 2399 Gateway Oaks Drive, Suite 200, Sacramento, CA 95833 Tel 916-288-6431 . Toll Free 888-526-6300 . Fax 916-288-6500 . http://www.sungard.com/products_and_services/swms/managed_account_soluti ons/default.htm <http://www.sungard.com/products_and_services/swms/managed_account_solut ions/default.htm> CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you. -----Original Message----- From: Patrick Quinn [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 26, 2005 4:04 AM To: [email protected] Subject: WSDL versus ?WSDL Hi This question is a variation on what I have asked before, but as yet had no response on. So I thought I'd rephrase it and make it more generic. How closely should the WSDL seen via http://<ipaddress>:8080/axis/services/<servicename>?wsdl approximate the original WSDL? I am seeing some noticeable differences between the two, and I need to ascertain whether this is: A) normal B) caused by a malformed WSDL C) the result of a malformed WSDD file D) an AdminService deployment bug I can provide an example if necessary. For the moment, if anyone can tell me which is the likeliest scenario then that at least is an avenue to pursue. I'm hoping it's A) or B) then at least I can do something about it. Thanks in advance Patrick This e-mail and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform Evolving Systems TIS at [EMAIL PROTECTED] and then delete the e-mail from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. To ensure regulatory compliance and for the protection of our clients and business, Evolving Systems may monitor and read e-mails sent to and from its servers. Although Evolving Systems routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Evolving Systems makes no representation or warranty as to the absence of viruses in this e-mail or any attachments. Registered Office: One Angel Square, Torrents Street, London. EC1V 1PL. Registered number 2325854
