Hi Eric,
Here is the build [1] which fixes all the issue you have currently
reported. This build is capable of forwarding the 500 Internal Server
Error as it is (i.e. as a text/html message) back to the client with the
attached configuration, also I have fixed the issue with the Hessian
Fault (not having the startReply and completeReply sections).
Further, if you want to change the 500 Internal Server Error comes as
text/html (or any html error) to synapse from Hessian service to a
standard Hessian Fault for the client, that also can be done with a
change in the configuration, to remove the contentType and messageType
properties and adding a property named HTTP_SC with value 200 under the
axis2 scope.
You should be able to pass your special cases with this. Please let me
know any issues of this build if there are any....
[1] - http://ww2.wso2.org/~ruwan/jamba/v4/wso2-esb-java-SNAPSHOT-bin.zip
Thanks,
Ruwan
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
