Eric,
I think I have specified the property for the 200 OK. (I forgot to
mention that it is different from the earlier build) I have changed it
to a generic property so that you can set any HTTP status. The new
property name is "HTTP_SC" and you can specify any HTTP status code as
value of this property for example to send a 200 OK the property will be;
<property name="HTTP_SC" value="200" scope="axis2"/>
Does the HTML forwarding works? I think when you are forwarding the HTML
response directly to the client you do not have to use the HTTP_SC
property because it will be automatically handled by the ESB and the 500
Internal Server Error status will be forwarded to the client (AFAIK,
that is your requirement right?)
Thanks,
Ruwan
Hubert, Eric wrote:
Hello Ruwan,
thanks for providing this build. Unfortunately I'm facing some problems.
Using the following Proxy-definition
<syn:proxy name="CAT" startOnLoad="true" statistics="enable"
trace="disable">
<syn:target endpoint="CAT_berehubert-d1">
<syn:outSequence>
<syn:property name="SC_OK" value="true" scope="axis2"/>
<syn:send/>
</syn:outSequence>
</syn:target>
</syn:proxy>
on my local windows machine I got the error recorded in error1.log.
Later some requests simply timed out. This was the same configuration
which worked with your last build.
If I use the following configuration
Ws
<syn:proxy name="CAT" startOnLoad="true" statistics="enable"
trace="disable">
<syn:target endpoint="CAT_berehubert-d1">
<syn:outSequence>
<syn:property name="SC_OK" value="true" scope="axis2"/>
<syn:filter xpath="//html">
<syn:property name="messageType" value="text/html"
scope="axis2" />
<syn:property name="ContentType" value="text/html"
scope="axis2" />
</syn:filter>
<syn:send/>
</syn:outSequence>
</syn:target>
</syn:proxy>
It works, but the http status on the client side is still 500 and the
SC_OK property seems to have no effect.
Please find attached the output of the trace-log for this call as
trace1.log.
Regards,
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
