Hi all,
If we consider interoperating with .NET and Axis, IMO doc/literal is
better than rpc/encoding
Mahen
On Fri, 10 Sep 2004 14:25:13 -0700, Nelson Minar <[EMAIL PROTECTED]> wrote:
> >Whilst everything Jim said is true, rpc/enc has been around the longest
> >in the current tools and I think
Hopefully some axis guru will tell me Im way off but my understanding the
problem is you would still loose interop since you still rely on knowing
what an exception is on the client side (?). Besides which I think you
probably want possible faults described in the wsdl so clients can figure
out exa
I'm migrating an Axis 1.1 Web service to 1.2, but I'm already at a loss. The
installation is OK, stock quote sample works fine, but every time I want to run my own
service, I send:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.
Set the timeout on the service to be 0 so that the socket will not be closed.
Sandeep
On Sun, 12 Sep 2004 19:52:08 -0400 (EDT), Anand Natrajan
<[EMAIL PROTECTED]> wrote:
> All,
>
> As part of the web services I am deploying, I have some methods that take a
> while to complete (in truth, they re
All,
As part of the web services I am deploying, I have some methods that take a
while to complete (in truth, they return so much data that it takes a while
to accumulate all of that).
When I was deploying Axis 1.2beta2 on the server and client side, everything
worked well with whatever defaults
Please comment on this pseudocode for exception handling.
The majority of the client and server code would throw
subclasses of DetailedException, which would not be axis-
specific. That would be converted to and from an
AxisFault, and a generic fault would be sent over the
wire (illustrated at
