Hi,
The basic hessian builder and formatter is almost complete. There is in
the response from a Hessian service.
It does not contain a content type. Hence, the Hessian builder is not
called when a response is received and it is not routed back to the
client, and a null exception occurs.
Yes ,if Axis2 can not find a content type this what normally happen
Can the synapse code be modified to address this issue.
I do not think it is a good idea and and also it is not the right
approach as well. For example if we do an async invocation with two
channel we will not be able to fix the problem just changing synapse code.
Same Hessian request:
POST /HessianSample/hessian/hello/?reponse=hessian HTTP/1.1
Content-Type: x-application/hessian
User-Agent: Java/1.5.0_11
Host: 127.0.0.1:7000
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 12
c
Sample Hessian response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Length: 19
Date: Wed, 05 Mar 2008 05:20:05 GMT
r
I think response should have the content type or there should be a
mechanism to obtain the content type.
Thank you,
Deepal
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
