Hi , Thanks for the point. But how can you explain that I have a service on apache soap server ( a class that has some exposed methods ) and one of the methods throws an SOAPException . In fact throws my own exception that extends SOAPException . And it works . Well , last time it worked. Now I should try to re-deploy to see if is something wrong with my own code or .
Might be something wrong to the isd:faultListener from DeploymentDescriptor ? Anyway, what does the line with isdFaultListener from DD.xml means ? ( a little bit new to apache soap ) Please, can you tell me what do I have to change in order to make it work? Thanks , dovle > This is actually a bug in the apache code. I tracked it down for some > reason when a fault occurs, when the soap code sets a faultrouter in the > soap code the one that it is going to add to the list exists, but it > adds it, and then nothing is there. When it tries to access the list > there is nothing there and it throws the NullPointerException. I spent > some time on it, but I ended up having to just skip it so it never tries > to notify faultListeners. The NullPointerException is masking the > actual exception that occured. I gave a very detailoed description and > never heard anything else. You can search the archives for it. > > Rich Catlett >
