Tharindu
I think Axis2 looks at some property to locate the formatter/builder
before looking at the content type.. so can we make use of that to make
the correct builder get selected?
asankha
Tharindu Mathew wrote:
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.
Can the synapse code be modified to address this issue.
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
Thanks,
Tharindu
_______________________________________________
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
