Are there any plans for JBossWS to upgrade to Remoting 2.0.x and use the new
feature
http://jira.jboss.com/jira/browse/JBREM-425;jsessionid=506E94EEC425428E9D0B647DBCB56E7C
so that clients can indicate that they accept compressed transport data and
actually use the compression unmarshaller if
Tom,
Last week I looked at the code and it looks like JBoss Web Services would
require Remoting 2.0.0 with the JBREM-425
http://jira.jboss.com/jira/browse/JBREM-425;jsessionid=506E94EEC425428E9D0B647DBCB56E7C
fix. The JBoss Web Services client would need to make the proper invoke call
to add
Is Remoting used with JBossWS and if so can it be used to configure transport
compression? I am using JBossWS-1.0.4.GA along with JBossAS-4.0.4.GA. According
to what I have read JBoss Remoting has pluggable data marshallers and on the
Wiki it states that there exists data compression
There is a gotcha when you follow the install instructions and drop in
jbossws-1.0.4.GA into jbossas-4.0.4.GA and it has to do with updating the
jboss-xml-binding.jar library from jbossxb/1.0.0.CR7. The JBossAS contains a
library called jbossall-client.jar which a client of the JbossWS should
I discovered that there were performance fixes with JBossWS and with JBossXB so
I have followed the upgrade instructions and have upgraded to JBossWS-1.0.4.GA.
The Web Services do work faster now but we will still have a performance issue.
I would like to get transport compression working
I am using JBoss-4.0.4.GA and JBossWS-1.0.1.GA to develop JSR-109 POJO service
endpoints using the RPC/literal model. We are currently having performance
issues with large objects so I am trying to enable transport compression with
Tomcat. I've enabled compression in Tomcat per instructions in
