I'm exposing a method, that uses an interface as an
argument. Properties defined in that interface go into the
WSDL and the client-side stub code. However, that interface
extends another interface, which's properties don't appear
in the WSDL. Is this a feature or a bug?
Second: the stub generated
I defined a service, which uses a complex type. The complex
type (at the service side) is described by an _interface_.
Running the sources through Java2WSDL and WSDL2Java results
in a client-side class being generated for the complex type
which is _abstract_. Now, if I execute the service method,
Does anybody know about some guidelines on how to design web
service interfaces? I'm facing a couple of problems when
translating object oriented interfaces into traditional
RPCs.
Thanks, Ronald
You may want to try WASP. I believe its what you're looking
for.
Regards, Ronald Huetter
- Original Message -
From: "robert woodley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, 20. May 2002 21:43
Subject: javascript SOAP clients
> Dear All -
>
> I need to write a AXIS SOAP
I read here and there about persistent connections. Is AXIS
using these by default or can I configure for it? Will it
improve performance?
I expected, that if I deploy the service with the above
option, the constructor of the xxxImpl class would be called
only once per session. In fact I don't see any difference
compared to "Request" scope. Am I on the wrong track? How
can I instantiate a class as a session singleton?
Does anybody know, whether it is safe to call the same
service by multiple threads, resulting in overlapping calls?
BR, Ronald
I did not explicitly put any specific XML parser on the
classpath. How can I know, which one is used and which one
would give me the best performance?
Ronald
