Just to be clear, I think the issue we're talking about is that Axis
is converting our applications exceptions into AxisFaults, but we don't
have as much control over the structure of this AxisFaults as we like.
For me the issue seems to be that AxisFault.makeFault() is hardwired
pretty deep in Ax
I would need custom exceptions too and, as Sacha said, it's not a good idea to build a
strong dependency to Axis classes.
In my project I have to implement an API which offers an web service and I would like
to let a customer decide what SOAP middleware to be used.
Right now it's str
> Have you tried extending AxisFault? That's what we do and it seems to
work well enough...
Hi.
Thanx for reply. I don't think it is a right way. It strictly tides You to
axis architecture of Your service. In my situation I want to have web
service interface to EJB deployed on JBoss. Methods of
/2004 Subject: custom exceptions
02:35 PM
Please re
Hi.
Has anybody any experience with custom exceptions in axis? I
tried to throw my own checked exception, but always get AxisFault,
containing only stack trace as details and Server.userException as a fault
code.
I looked into the axis source code and it seems there is no way to throw
custom
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 10:20 AM
To: [EMAIL PROTECTED]
Subject: Custom Exceptions & non-axis clients
I know this has been discussed before here, but I can't seem to find a solution.
Hoping someone can provide assistance.
I
I know this has been discussed before here, but I can't seem to find a solution.
Hoping someone can provide assistance.
I've created a custom exception class with some extra error info which I want my
service methods to throw. When I run wsdl2java, Axis creates the class as a subclass
of org.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682
http://marc.theaimsgroup.com/?l=axis-dev&m=105354748107569&w=2
-- dims
--- Dan Kamins <[EMAIL PROTECTED]> wrote:
>
> How specifically has this problem been fixed? I'm looking at the samples/faults
> example in v1.1
> and I can see now tha
How specifically has this problem been fixed? I'm looking at the samples/faults
example in v1.1 and I can see now that a RemoteException (not AxisFault) is being
thrown, and that it has a bean typeMapping in the wsdd. But what control does a
developer have over this mapping? This should be e
We are NOT going to change the way wsdl2java generates code...In 1.1, you can register
your own
exceptions and throw/catch them. Look at samples\faults
-- dims
--- Peter Landmann <[EMAIL PROTECTED]> wrote:
>
> Dear Dvanum,
>
> Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > Dan,
> >
> > This p
Dear Dvanum,
Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Dan,
>
> This problem has been fixed already in 1.1
I am using the 1.1 release version (I never tried it with 1.0). Last week I
even tried one of the nightly builds, but the problem is still the same,
and wsdl2java generates the same exc
Dan,
This problem has been fixed already in 1.1
thanks,
dims
--- Dan Kamins <[EMAIL PROTECTED]> wrote:
>
> I faced the same problem (can't throw app-specific exceptions) and solved it by
> subclassing
> AxisFault for all of my exceptions. It allows me to explicitly set text for the
> actor,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
Hi,
Once again, as no one replied: Did really no one else face this problem up
to now? Don't you use exceptions in your service interfaces?
I took a look on the JAX-RPC specification 1.0 now: It defines that service
specific exceptions must extend java.lang.Exception - and not something
like Remo
Hello all,
I use Axis 1.1 and would like to work with custom exceptions. I generated
the client side code with wsdl2java, and the generated client stub
correctly declares these exceptions, but unfortunately the deserialization
doesn't seem to work: I get an AxisFault instead of my self-de
nt to keep my business logic interfaces (and the exceptions which belong
to it) as independent from the underlying RPC technology as possible. Does
this really mean that it is not possible to use custom exceptions which are
not derivated from AxisFault?
Regards,
Peter Lan
-Original Message-
> From: David Owens [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 13, 2002 11:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Custom Exceptions
>
>
> Sam/Sylvain
>
> Bob is on vacation, but I worked with him on this stuff, so I
> thought I'
That is interresting. Thanks for the code.
Sylvain.
-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: Custom Exceptions
Sam/Sylvain
Bob is on vacation, but I worked with him on this stuff, so I
xiFault
> >shouldn't I be able to throw a descendent of AxisFault and, assuming it is a
> >known type, expect the serialization to occur?
> >
> >Sylvain.
> >
> >
> >-Original Message-
> >From: Bob Cotton [mailto:[EMAIL PROTECTED]]
> >
serialization to occur?Sylvain.-Original Message-From: Bob Cotton [mailto:[EMAIL PROTECTED]]Sent: Tuesday, June 11, 2002 8:41 PMTo: [EMAIL PROTECTED]Subject: Re: Custom Exceptions
"Sam" == Sam Kapoor <[EMAIL PROTECTED]> writes:
it is aknown type, expect the serialization to occur?Sylvain.-Original Message-From: Bob Cotton [mailto:[EMAIL PROTECTED]]Sent: Tuesday, June 11, 2002 8:41 PMTo: [EMAIL PROTECTED]Subject: Re: Custom Exceptions
"Sam" == Sam Kapoo
esday, June 11, 2002 8:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Custom Exceptions
>>>>> "Sam" == Sam Kapoor <[EMAIL PROTECTED]> writes:
Sam> Hi: what I want to do is write a custom exception class and
Sam> propagate it from one of the methods on my
Hi Sam,
As Bob Cotton mentioned, we are currently working on this, however, our
challenge is to get the data from our custom exception sent over as
well. If your custom exception does not have any ivars, it should work
with the lastes version of the axis code. You do, however, have to
catch you
Hi:
what I want to do is write a custom exception class and propagate it
from one of the methods on my Web-Service to the client. So I define
a Java exception class:
public class EInvalidCustomer extends Exception {
public EInvalidCustomer(String err){
super(err);
}
The method on my we
> "Sam" == Sam Kapoor <[EMAIL PROTECTED]> writes:
Sam> Hi: what I want to do is write a custom exception class and
Sam> propagate it from one of the methods on my Web-Service to the
Sam> client. So I define a Java exception class:
Sam> public class EInvalidCustomer extends E
Hi:
what I want to do is write a custom exception class and propagate it
from one of the methods on my Web-Service to the client. So I define a
Java exception class:
public class EInvalidCustomer extends Exception {
public EInvalidCustomer(String err){
super(err);
}
The method on my web-s
29 matches
Mail list logo
