Posts

Showing posts with the label CXF

What does: "Fault occurred while processing" in the client mean? and how do you reveal the real exception?

I have this CXF client which sometimes throws normal exceptions but some of the other times it throws me a "Fault occurred while processing", well, what does that mean? When you get back a "Fault occurred while processing" it means that a web service threw an unchecked exception.  The CXF framework catches it and puts together a fault message which it sends back to the client.  The client’s stack trace at that point is pretty-much irrelevant . There may be a way to get CXF to log the server stack trace, but I haven’t found it yet (feel free to comment on the post if you found one).  There may also be a way to stick a handler into the flow to get the exception before constructing the fault message, but I haven’t found that yet either (ditto). If a checked-exception is thrown, then the exception – or at least its message – gets sent back to the client where it’s reconstructed and rethrown to be caught by the client. Debugging a problem like this, o...

Bad Unmarshalling of a CXF object which results in a null object

The story in short: I have a webservice which gathers some information from my DB, creates an object containing the info, then sends it to my client. Sounds like a simple CXF webservice scene? Well, for the last two days i'm fighting it; why? Cause my client gets only a nullified object, it's quite frustrating... So i caused some logs to appear and discovered that - The SOAP message actually contains the whole Object. My client just can't build it (Unmarshal it) into the object it's supposed to be. So, whose fault is it and how do I fix it? Aegis' binding is my guess (not that it helps much), so that's the road i'm taking. What did I find (OK, what did my boss find?) ? Here are some interesting things that I learned in the process of getting the Peering WS client to connect up with the Peering WS: The basic mechanism for serializing and deserializing the data of a web service is the databinding implementation.  I’ve been using Aegis, which is described ...

WARNING: Can't find the the request for http://127.0.0.1:8080/... 's Observer

When did this stackTrace been thrown? While running a CXF webservice over a tomcat server. Scenario: My client (client software) tries to connect the CXF webservice, but the following line keeps being stacked at my server's console windows: WARNING: Can't find the the request for http://127.0.0.1:8080/... 's Observer What's the problem? After thorough investigation I tried invoking a services list using my web browser - And a list I got! Where I found out that I wrote the wrong endpoint Mystery solved :-)