axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pär Malmqvist <>
Subject RE: Axis2-1.5.1 and user exceptions
Date Sat, 20 Feb 2010 08:19:25 GMT


I have been waiting for code-first approach to handle custom exceptions for about three years

So I always have to use contract-first approach to get it to work.
Its really time consuming but not much to do.

Pär Malmqvist

Date: Fri, 19 Feb 2010 09:15:03 -0500
Subject: Re: Axis2-1.5.1 and user exceptions

I have been puzzled by this issue for long time. Seams like at this point, using contract-first
approach is the only solution for now.
But it will still be very very helpful if something can be done so code-first approach can
work too. Axis1 definitely worked. I can imagine lots of people are using code-first approach
because of its simplicity.


On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari <> wrote:

Il 17/02/2010 3.53, glopezm ha scritto:

Any thoughts/experiences with a similar issues with axis2?

I use contract-first approach. My user exceptions extend Exception and have a field called
faultMessage with getter getFaultMessage and setter setFaultMessage. The constructor prepares
the faultMessage and sets it via setFaultMessage. The faultMessage is an object of a class
generated by WSDL2Code from an XMLSchema type that describes my fault message, so that it
implements ADBBean.

In this way, when my code raises my user defined exception, Axis2 recognizes the existence
of the fault message and attaches it correctly to the fault returned to the client code.

This is the result of my trial-and-errors researches of some years ago with Axis2 1.3 and
it is working with Axis2 1.5 too. I think that you may find something else in this mailing
list archive by me on this subject.


Mauro Molinari

Software Designer & Developer


Li Ma

Hotmail: Powerful Free email with security by Microsoft.
View raw message