axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From glopezm <>
Subject Re: Axis2-1.5.1 and user exceptions
Date Sat, 17 Apr 2010 14:59:23 GMT

Thanks for your reply!
Just as an update I wanted to state that I've resolved this issue by moving
on to the axis2 jaxws implementation which works pretty good so far and
exceptions work like it is expected. Using this approach you can develop
contract last web services without spending too much time.

Regarding the contract first approach, I think it is a good practice but
almost just for the books. This is for me (saying that with all my respect
for other opinions) almost impossible to do in the real world since you
always have a tight schedule to develop an application and web services are
just a small part of it (the interface). It is not possible/reasonable to
dedicate such a long time while you have more important things to resolve
like the the core business internal implementation. I'm not saying that one
do not have to pay attention to web services and compatibility issues that
may come with contract last, but it is not a fact that you'll have problems
if you do it and even though all issues can be resolved. This is just my
opinion :-).

Regardless of what I stated, I recognize that under certain conditions
contract first might be a better approach. 

Thanks again for the help!!!

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
> E-mail:

View this message in context:
Sent from the Axis - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message