Re: [soapbuilders] Re: XMLBus endpoints updated
> SOAP4R client - XMLBus server test result: 74/82 => 78/82We definitely don't have any plans to support this anytime soon. msec
> 1. DateTime with long precision such as
> No one won't complaint about this.
accuracy is "good enough" for us. (Basically, it has to do with the JAVA
Calendar object that we use for dates. It only goes to msec.)
> 2. Sending a parameter to echoBase64 with not XSD:base64BinaryPersonally, I think the test for this is invalid. According to the
> but SOAP-ENC:base64 encoding. WSDL defines its type as
> XSD:base64Binary so this test should fail.
description of the Round 2/Base service at:
the parameter should be xsd:base64Binary. If you are sending something
other than that, then your test isn't testing Round 2/Base endpoints.
(unless you are testing to see if the server throws a fault) If the
server is expecing a SOAP-ENC:base64 object, then that server is not a
proper Round 2/Base endpoint.
Anyway, I feel what we are doing here is correct.
> 3. [out] parameter haven't supported in XMLBus yet?Nope, not yet. It's getting higher and higher on the priority list
> I'm very very happy with excellent interopping(?) with XMLBus.Thanks for creating a fairly comprehensive set of test cases to point
out some of the problems. It's definitly been a big help.
J. Daniel Kulp
END 2 ANYWHERE
P: 781-902-8727 C: 617-513-4582 F:781-902-8001
- I tried using your web client to test out GLUE, and had major problems
with a few things. Your static client failed everywhere, with a Remote
Exception, wrapping an IOException, wrapping a FileNotFoundException.
(See attached Stack Trace.) The proxy client did well, except for
echoHexBinary and echoVoid.
//Stack Trace follows
java.rmi.RemoteException: Error doing soap stuff; nested exception is:
at java.lang.reflect.Method.invoke(Native Method)