Hi, I think the problem comes from client side, where depending on jax-ws
library you use (if it's embedded into JDK or not) you have to specify
different property name to enable fast-infoset. If you use jax-ws embedded
into JDK, pls use this property [1], otherwise try [2]. For example for JDK
embedded jax-ws the code will look like: ((javax.xml.ws.BindingProvider)
_port).getRequestContext().put("com.sun.xml.internal.ws.client.ContentNegotiation",
"pessimistic"); The first HTTP request on wire will look like: POST
/FastInfosetTest/ByteArrayService HTTP/1.1 Content-type:
text/xml;charset="utf-8" Soapaction:
"
http://bytearray/ByteArrayService/postRequest" Accept:
application/fastinfoset, text/xml, multipart/related, text/html, image/gif,
image/jpeg, *; q=.2, */*; q=.2 User-Agent: JAX-WS RI 2.1.6 in JDK 6 Host:
localhost:8080 Connection: keep-alive Content-Length: 201 The proper
fast-infoset content-type is application/fastinfoset. The content-type
application/fastsoap is related to fast webservices. fast webservices !=
fastinfoset ;) Looks like in your usecase you try to transfer huge amount of
binary data, even though I'd expect FastInfoset to perform faster than plain
XML... it's not the main FastInfoset usecase. On other hand FastInfoset may
outperform XML greatly when you transfer XML documents (not binary data).
Thanks. WBR, Alexey. [1] com.sun.xml.internal.ws.client.ContentNegotiation
[2] com.sun.xml.ws.client.ContentNegotiation
--
[Message sent by forum member 'oleksiys']
View Post: http://forums.java.net/node/890126