Sean,
I was looking at your pom files for the sample. I'm wondering if we
could get rid of the env.CXF_VERSION requirement by using version
ranges and profiles and such.
I've attached an modified versionof the wsdl_first for you to look at.
First, it defines a cxf.version property (def
On Jul 18, 2008, at 11:49 AM, Mohan Radhakrishnan wrote:
Hi,
Lots of helpful information.
Looks like gathering some performance metrics about CXF JAXWS
+JAXB
also could be an important criterion. Do you have suggestions to
measure
this type of metric ?
We have a "benchmark" di
On Jul 18, 2008, at 1:20 PM, Glen Mazza wrote:
Would you say that the number of web service providers that require
the
content-length field is decreasing over time? Certainly, not too
many CXF
installations would require it.
Over time, it would definitely be decreasing. The major pro
Would you say that the number of web service providers that require the
content-length field is decreasing over time? Certainly, not too many CXF
installations would require it.
I only remember the eBay client having that problem of requiring the Content
Length field--but CXF has been fixed to o
I'm getting kind of sick of saying "turn off chunking" so I've been
experimenting with the benchmarks to see what we can do and also get a
feel for what we lose/gain with it.
First thing I've learned: you REALLY want to use the ParallelGC stuff
on multi-core systems. Huge boost with tha
Hi,
Lots of helpful information.
Looks like gathering some performance metrics about CXF JAXWS+JAXB
also could be an important criterion. Do you have suggestions to measure
this type of metric ?
Moreover one reason we use XMLBeans for our client is because they
want w3c comp
On Jul 17, 2008, at 9:01 PM, Glen Mazza wrote:
Oh I see--I think you already merged the WSS4JInInterceptor one in
2.0.x, it's just the WSS4JOutInterceptor we're talking about. I'm OK
either way about changing the code because regardless, I think I can
rephrase the CXF documentation anyway and
