thanks for the tip Steve - looks like this isnt just me so ive made it a bug
report.
/tom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 11:28 AM
To: [EMAIL PROTECTED]
Subject: Re: wsdl2java fault bug ?
You need to hand modify the wsd
il get confirmation from a dev then jira it i guess - mostly going to be php
clients in my case so i havent resorted to a work around yet.
/tom
-Original Message-
From: Silvano Maffeis [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 10:21 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PRO
Anyone else observed that when you have code that throws multiple possible
faults, the generated stub assumes that the fault is always the last
defined ?
in this case, if you throw SomeOtherFault and verify that the XML going
over the wire correctly reflects the fault, client side it assumes the
f
could be anything, id suggest where you have your SoapBindingImpl class,
you call the relevant method from a jsp or similar to help track it down
server side. your probably missing a jar somewhere.
/tom
> Hi all,
>
> I'm generate Java objects with the WSDL2Java tool
> I have a simple service r
from memory the nosuchemployee extends remote exception (as opposed to
extending axis fault) hence you see an exception client side. the
recommended way is to use faults as opposed to exceptions for interop. the
fault sample included in axis1.1 isnt especially good in my opinion -
Richard Hanson p
im no expert but i think you should be extending axisfault if you want
interop.
/t
> Hey Everyone,
>
> I have written a service using Axis, and can throw and catch exceptions
> with
> no problem using Axis generated clients and JWSDP generated clients.
> However, whenever I wrote a .NET client an
Yep (axis 1.1) - have you tried the samples.faults package in the axis /
samples ?
/t
> Has anyone written user defined Exceptions, extending the
> java.lang.Exception class and successfully thrown them from the server
> side
> and caught them at the client side? Currently, whenever I try to thr
your XObject goes over the wire as xml representing the information
contained within in - the XObject implementation specifics arent carried
across.
/t
-Original Message-
From: Paul Callahan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 14, 2004 2:40 PM
To: [EMAIL PROTECTED]
Subject:
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
Im certainly no expert and I was asking the same thing but from my
understanding, you can extend remote exception and catch them but you
loose interop so the best way is to extend axis fault and use constants to
set fault codes which you can then get at client side. The catch is you
cant (or I cant
Hi
All,
Ive been trying to
figure out the best way of doing exception / error handling. If someone could
give me some guidance it would be much appreciated. Ive made some assumptions
from reading various docs - please correct me. Im using Axis 1.1 (Java), +
latest Tomcat.
As I understan
11 matches
Mail list logo
