We do have an on/off switch on WSDL2Java, but just because extra stuff gets added to the WSDL doesn't mean we notice or care in our current tests.
There should be a test that gets WSDL from a skeleton web service and verifies that the get*Desc functions do not show up. -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: RE: (Attn:Tom and others) EsrTest What we really need is a skeleton on/off switch. We talked about this at one point and gave it up because I don't think it would have been easy to implement. We settled for doing half our tests with skeletons and half without (yeah, lame, I know). Would it be easier to add such a switch with our new build process? Russell Butek [EMAIL PROTECTED] Tom Jordahl <[EMAIL PROTECTED]> on 09/27/2002 09:16:21 AM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: (Attn:Tom and others) EsrTest Yes, I noticed this and mentioned it to Russell on the chat. I then promptly forgot to follow up with Email. This stuff broke a while (>3 months) ago as well and was fixed then, by Russell I think. If you guys want skeletons to stay in the system, you are going to have to keep closer track when they break. :-) We should have a test case. -- Tom Jordahl Macromedia Server Development -----Original Message----- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 6:07 PM To: [EMAIL PROTECTED] Subject: (Attn:Tom and others) EsrTest The wsdl/esr test uses skeleton deployment. Is this by design? ?WSDL processing is incorrectly returning the special skeleton methods, like getOperationDescByName. By the way shouldn't static methods be excluded during ?WSDL processing. Rich Scheuerle IBM WebSphere & Axis Web Services Development 512-838-5115 (IBM TL 678-5115)
