axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kahler, Jason J \(US SSA\)" <>
Subject RE: Soap Faults and Exception
Date Tue, 16 Oct 2007 11:30:57 GMT
I think I fixed it after making changes to my wsdl.

I think my problem is that I was using the name ServiceException for to




From: Amila Suriarachchi [] 
Sent: Tuesday, October 16, 2007 12:41 AM
Subject: Re: Soap Faults and Exception


can you send your wsdl?

On 10/15/07, Kahler, Jason J (US SSA) <>

I am using adb. I don't think it is a wsdl issue, because this wsdl
generated Service.Exception fine using Axis 1.

I also have only one method in my wsdl that throws that fault. It does
in fact generate the Fault classes. But they do not extend Throwable.



From: Amila Suriarachchi [] 
Sent: Monday, October 15, 2007 1:06 AM
Subject: Re: Soap Faults and Exception


what is the data bind you use?
Axis2 generates a seperate class for every element. and each fault
message. so if an element with the wsdl namespace with the name same as
the fault message then both classes would have the same package and
class names. 

to avoid this use -p option to specify a seperate package name for wsdl

On 10/12/07, Kahler, Jason J (US SSA) <
<> > wrote:

I am using Axis2 1.3 

I have defined a custom Fault in my WSDL. It worked fine using axis 1.

But now when I run WSDL2code via the maven2 pluggin I get errors when I
try to compile my classes such as:


java:[63,17] incompatible types

found   : wfnp.ServiceException

required: java.lang.Throwable


the wfnp.ServiceException class doesn't even extend any kind of
throwable, so how can my classes actually

throw it ? I am very frustrated and confused.




Amila Suriarachchi,
WSO2 Inc. 

Amila Suriarachchi,
WSO2 Inc. 

View raw message