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

Attachment: error1.log
Description: error1.log

Attachment: trace1.log
Description: trace1.log

_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to