I am looking at making the changes requested by Thomas...
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Russell Butek
To: R J Scheuerle
Jr/Austin/IBM@IBMUS
02/08/2002 08:32 cc:
AM From: Russell
Butek/Austin/IBM@IBMUS
Subject: RE: Changes in current build
vs. alpha3 in WSDL generation: New problems
with .NET 1.0 (bugs found and fixes
provided)
Actually, I think this question is for you...
I don't know why he thinks there's a problem.
Russell Butek
[EMAIL PROTECTED]
---------------------- Forwarded by Russell Butek/Austin/IBM on 02/08/2002
08:32 AM ---------------------------
Thomas Börkel <[EMAIL PROTECTED]> on 02/08/2002 03:13:05 AM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Changes in current build vs. alpha3 in WSDL generation: New
problems with .NET 1.0 (bugs found and fixes provided)
HI!
I tested the latest build from 2002-02-07 and there the problem is not
fixed.
Please let me know how Russell want to deal with the appended "Service"
problem.
Regards,
Thomas
-----Original Message-----
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Donnerstag, 7. Februar 2002 22:58
To: '[EMAIL PROTECTED]'
Subject: RE: Changes in current build vs. alpha3 in WSDL generation: New
problems with .NET 1.0 (bugs found and fixes provided)
Hi Thomas!
I'm going to let Russell deal with your first problem, but I think Tom and
I resolved the second one with our last fix. Can you check to see if the
current CVS works for you? Thanks!
--Glen
-----Original Message-----
From: Thomas Börkel [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: RE: Changes in current build vs. alpha3 in WSDL generation: New
problems with .NET 1.0 (bugs found and fixes provided)
OK, I found both problems I mentioned below by myself after a debug
session (I don't like this very much):
1. "Service" is being appended to the name of the service:
org.apache.axis.wsdl.fromJava.Emitter, writeService(), line 497:
Current:
service.setQName(
new javax.wsdl.QName(implNS, getServiceName()+"Service"));
I changed it to:
service.setQName(
new javax.wsdl.QName(implNS, getServiceName()));
2. name attribut is missing in the response message:
org.apache.axis.wsdl.fromJava.Emitter, writePartToMessage(), line 754:
Current:
part.setName(param.getName());
I changed it to:
if(request)
part.setName(param.getName());
else
part.setName("Result");
.NET and I are now really happy (for the moment). Question is: Will you
apply my proposed changes to Axis and when?
At least change number 1 doesn't look like a bug, but like intention on
your side. Then please at least make this configurable. I don't like
"Service" being appended to every proxy class I generate in .NET.
Regards,
Thomas
-----Original Message-----
From: Thomas Börkel
Sent: Donnerstag, 7. Februar 2002 16:47
To: [EMAIL PROTECTED]
Subject: RE: Changes in current build vs. alpha3 in WSDL generation: New
problems with .NET 1.0
If I change the Response definition of the current build, then .NET is
happy:
Normal output from the current build:
<wsdl:message name="parameterTestResponse">
<wsdl:part type="SOAP-ENC:string"/>
</wsdl:message>
Manuelly changed WSDL to:
<wsdl:message name="parameterTestResponse">
<wsdl:part name="parameterTestResult" type="SOAP-ENC:string"/>
</wsdl:message>
Why is this?
-----Original Message-----
From: Thomas Börkel
Sent: Mittwoch, 6. Februar 2002 21:40
To: Axis Mailinglist
Subject: Changes in current build vs. alpha3 in WSDL generation: New
problems with .NET 1.0
HI!
Why does the current build always append "Service" at the service name?
Alpha3 did not do that and that was good.
Also, .NET issues an error now on the WSDL file:
Unable to import binding 'SoapTestSoapBinding' from namespace '
http://p2test.p2plus.apag.com'.
I am no SOAP expert, so I cannot tell what to do about this.
This is my test class:
public class SoapTest {
public String parameterTest(short s, int i, double d, String t, boolean
b)
{
System.out.println(s);
System.out.println(i);
System.out.println(d);
System.out.println(t);
System.out.println(b);
return(t);
}
public void exceptionTest() throws Exception
{
throw new Exception("Message");
}
}
This is how I generate the WSDL:
emitter = new Emitter();
emitter.setCls(Class.forName(completeName));
emitter.setAllowedMethods(allowedMethods.toString());
emitter.setServiceName(className);
emitter.setIntfNamespace("http://"; + packageName +
".p2plus.apag.com");
emitter.setUseInheritedMethods(true);
emitter.setLocationUrl("http://localhost:2037/"; + packageName +
"/" + className + ".jws");
def = emitter.getWSDL();
doc = WSDLFactory.newInstance().newWSDLWriter().getDocument(def);
bos = new ByteArrayOutputStream();
XMLUtils.PrettyDocumentToStream(doc, bos);
xml = bos.toString();
And please find the alpha3 and the current version of the WSDL attached.
The alpha3 version had a problem because of the void returntype (please
see other mail from me ".NET ignores methods with void returntype"), so I
wanted to check the current build. But this WSDL does not work at all with
.NET (it does not even generate proxy classes for it).
Thanks for any help!
Regards,
Thomas
