RE: WSDL Problem

2001-10-05 Thread Neil Smyth 

I've had the same problem when using the wsdl4j toolkit. If you step through
the Definition returned from the wsdl4j toolkit, you'll find that it doesn't
find the referenced binding node - because it is looking in a different
namespace. I've found this problem with a good subset of the wsdl files from
xmethods.

Given that you are generating the wsdl from another tool in the wstk, I'd
classify it as a bug with the generating tool. I'm also not sure about what
the correct syntax as per the wsdl spec is, anyone have any pointers on
that? Should the binding reference always be namespace qualified or not?

If you can find an easy way around this please let me know! I've resorted to
doing basic xml tree searching for the time being which is far from ideal :)

Regards, 

Neil

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 05 October 2001 17:24
To: [EMAIL PROTECTED]
Subject: WSDL Problem




Hi

I have created a java class which has one method square taking a double and
returning a double.  I have deployed this class to SOAP.
I have genereated WSDL via IBM wstk tool. I am using WSIF to try and
dynamically
read the WSDL and invoke the method,  but I cant seem to call it without
making
some changes to the WSDL that was generated.

If I add "tns:" to port binding i.e.

RE: StringOutOfBoundsException when invoking

2001-09-21 Thread Neil Smyth 

Ok, I found the problem: the response has a blank line in it that causes a
problem in the org.apache.soap.util.net.HTTPUtils post() method.

The soap response is
==
 
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";> 
 
http://schemas.xmlsoap.org/soap/encoding/";>
X 


 

==

I notice the fix is in the latest nightly source...

Regards,

Neil

-----Original Message-
From: Neil Smyth [mailto:[EMAIL PROTECTED]]
Sent: 20 September 2001 16:23
To: '[EMAIL PROTECTED]'
Subject: StringOutOfBoundsException when invoking


I'm using Apache Soap v2.2, and by and large it is working fine in calling
basic services over the web. However when I call the service at

http://www.ebob42.com/cgi-bin/Romulan.exe/soap/IRoman
 ===
public static void main(String[] args) {
try {
  // Build the call.
  Call call = new Call();
  call.setTargetObjectURI("URIurn:Roman-IRoman");
  call.setMethodName("IntToRoman");
  call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
  Vector soapParams = new Vector();

  soapParams.addElement(new Parameter("Int", int.class,
new Integer(10), null));
  call.setParams(soapParams);

  // make the call: 
  Response resp = call.invoke(new
URL("http://www.ebob42.com/cgi-bin/Romulan.exe/soap/IRoman";), 
  "");
} catch (Exception e) {
  System.out.println(e.toString());
}
  }
===
gives result 
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

I get a StringIndexOutOfBounds in the invoke() method. Has anyone else come
across this or something similar? It looks to me like it might be a soap
compatibility issue as the service is hosted on another implementation
(delphi).

Comments/thoughts appreciated!

Neil

Neil Smyth
Senior Software Engineer, Altio
T: +44(0) 20 8580 4519
F: +44(0) 20 8580 2050
nsmyth_at_altio.com
http://www.altio.com

StringOutOfBoundsException when invoking

2001-09-20 Thread Neil Smyth 

I'm using Apache Soap v2.2, and by and large it is working fine in calling
basic services over the web. However when I call the service at

http://www.ebob42.com/cgi-bin/Romulan.exe/soap/IRoman
 ===
public static void main(String[] args) {
try {
  // Build the call.
  Call call = new Call();
  call.setTargetObjectURI("URIurn:Roman-IRoman");
  call.setMethodName("IntToRoman");
  call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
  Vector soapParams = new Vector();

  soapParams.addElement(new Parameter("Int", int.class,
new Integer(10), null));
  call.setParams(soapParams);

  // make the call: 
  Response resp = call.invoke(new
URL("http://www.ebob42.com/cgi-bin/Romulan.exe/soap/IRoman";), 
  "");
} catch (Exception e) {
  System.out.println(e.toString());
}
  }
===
gives result 
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

I get a StringIndexOutOfBounds in the invoke() method. Has anyone else come
across this or something similar? It looks to me like it might be a soap
compatibility issue as the service is hosted on another implementation
(delphi).

Comments/thoughts appreciated!

Neil

Neil Smyth
Senior Software Engineer, Altio
T: +44(0) 20 8580 4519
F: +44(0) 20 8580 2050
nsmyth_at_altio.com
http://www.altio.com