Did you ever get this resolved, tomstrummer? I'm having the same issue and
can't seem to get it corrected.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232028#4232028
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=42
Thanks Alessio.
I found this documentation which I think you're referring to:
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_Client_Configuration
So, can I define my own jaxws-client-config.xml that will by default be used by
my WS client? Or do I have to call the service.getPort..
Or simply use the already provided HTTP 1.0 Client configuration:
|
| HTTP 1.0 Client
| http://org.jboss.ws/dispatch/validate
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185053#4185053
Reply to the post :
http://www.jboss.com/i
You can use the jaxws-config deployment descriptor and set the chunksize to 0,
see the standard-jaxws-client-config.xml for instance:
|
| Standard Client
| http://org.jboss.ws/dispatch/validate
|
| http://org.jboss.ws/http#chunksize
| 2048
|
|
Right, after looking a bit I am thinking the same thing -- the server simply
has a bug that prevents it from correctly handling chunked requests.
Unfortunately, the link you provided didn't seem to lead me to any solution as
far as JBossWS. I am providing the web service client but the server
The server might not be able to correctly handle http 1.1 connections using
chuncked transfer-encoding. See here for possible solutions:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971616
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183895#418
It seems that my suspicions are right; when "Transfer-Encoding: chunked" is
used, I get the 500 error. So is there any way to make JBossWS _not_ stream
the request body?
The server appears to be WebLogic if it makes any difference...
Thanks again.
View the original post :
http://www.jboss.co
