Eric,
I was able to generate the html fault by deleting some classes from the
sample war. I will get back to you once I found a workaround for the issue.
Thanks,
Ruwan
Ruwan Linton wrote:
Hi Eric,
I couldn't reproduce this. Basically I have tried to generate a
hessian fault by letting the hessian application to generate a runtime
exception, but it has been sent to the client as an HTTP 200 OK with
the stack trace. How can I generate a hessian fault of the type that
you encountered?
Thanks,
Ruwan
Ruwan Linton wrote:
Eric,
Give me the weekend, I will give you a solution
Thanks,
Ruwan
Hubert, Eric wrote:
Hello Ruwan,
Well, HTTP 500 Internal Server Error can be handled by the ESB, and
the
SOAPFaults are always comes with a HTTP 500 Internal Server Error,
with
application/xml as the content type. Here the issue is not the HTTP
500
message but the content of the message body being HTML. Well I will
work
on this and find a workaround for this within this week.
Could you find a workaround for this?
Regards,
Eric
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
