ansaurus

Question

Replace JBoss error page with Axis2 fault XML response

Answer 1

+1 A:

Without details of the exception, I can only speculate that the web service implementation is throwing a runtime exception that is not an instance of the SOAPFault or AxisFault classes (or their children). The default behavior in JBoss, in a such a case, would be to deliver the error page in the response, since web services are servlets after all.

That usually indicates that the web service must handle the exceptions appropriately and throw an appropriate SOAP fault, to prevent the exception from trickling up the call stack.

Update

A stacktrace would help in establishing the root cause of this issue. But I'm going to shoot in the dark anyway :)

You can refer to the issue RAMPART-164 and see if that is the actual cause of the problem. To put it briefly, from the information available, one can use SOAP 1.2. I'm not sure about the fix having been propagated to AXIOM 1.2.8 though, since I did not see any reference to WSCOMMONS-343.

Vineet Reynolds 2009-04-01 21:28:56

Sorry for the big delay but I was working on other projects. Four months ago I meant about the HTML page returned by JBoss/Tomcat in 500 errors.I tried to throw an AxisFault instead, but it does the same.I'm working with an Axis2 webservice with Rampart module and this last throws an exception if the client doesn't authenticate.

Dario 2009-08-04 15:47:52

By the way, there is an excellent post about Rampart and the correct way to authenticate users: http://blog.sweetxml.org/2007/12/rampart-basic-examples-how-you-add-ws.html

Dario 2009-08-04 16:03:54

Looks like you're not the only one : http://www.mail-archive.com/[email protected]/msg47665.html

Vineet Reynolds 2009-08-05 19:07:54

I tried to upgrade to AXIOM 1.2.8, but it fails in the same way. Tomcat returns its standard 500 error HTML page instead of SOAP fault response.

Dario 2009-08-11 08:33:41

I'm going to give a try to AXIOM trunk, as said in http://markmail.org/message/lg4iuc7yiogwiqh3

Dario 2009-08-11 08:57:13

I didn't work too. Anyway, Vineet helped me a lot with the reference, so I give to him the current bounty.Maybe I'm doing something wrong with the compiled jars I get with Maven, but today I can't take more time around this.

Dario 2009-08-11 15:07:23

Suprisingly, I changed my IDE (from Eclipse Galileo to Netbeans 6.7), download again Axis 1.4.1 and Rampart 1.4 and it works.The other thing changed is Tomcat, now working with 6.0, but I don't think it is the cause!Vineet, anyway, thanks a lot for your help!

Dario 2009-08-12 16:18:13

That's surprising. Nice to know that it works. It could possibly be a classloader related issue or it could be the JARs obtained from Maven.

Vineet Reynolds 2009-08-12 16:54:24

Answer 2

A:

There is a bug in rampart-core jar file. MessageBuilder in RampartSender is expecting AxisService in message context while sending the response back to the client. In this case it is null which throwsa NUllpointer exception. Add a null check in the RampartMessageData and rebuild the rampart core jar and use it. The application should work fine.

AxisService service = msgCtx.getAxisService(); if (service != null) { this.customClassLoader = msgCtx.getAxisService() .getClassLoader(); }

-Mahesh Yarasi

2010-05-04 14:58:01

ansaurus

tags:

views:

answers:

Replace JBoss error page with Axis2 fault XML response

related questions