Hi,
Same with the JAX-RS JAXB (and JAXB based JSON) provider - contexts are
cached and can be reused.
If ObjectFactory is available then only a single context will be
created.
At the moment, either a class name or just a package name can serve as a
key in the (two) maps of contexts.
May be for
I'm honestly no seeing this on my linux box with the latest code. I hit it
with about 500K requests to warm up the JIT and stuff, check the heap sizes
using jconsole (1.6VM), then hit it with another 1.5 million requests and
rechecked the heap sizes and they ended up exactly the same.
On Saturday 11 October 2008 3:34:52 am Christian Schneider wrote:
Hi Dan,
sounds reasonable to me. I have added the config element to address and
set the default.
I think setting useJms11 to false for 2.0.x and 2.1.x probably makes sense for
compatibility sake. For 2.2 (trunk), it probably
Adding the Link again from the last post:
Could you please have a look at the following post and tell me whether it
applies to CXF.
http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java
~
anoopPrasad
anoopPrasad wrote:
Dear Dan/Bharat,
I have checked Heap,non-Heap, and
Hi Willem,
so that´s fine with me. I think we should start a release note wiki page
for 2.0.9 and perhaps also for 2.1.3.
Btw. I noticed that there is no release notes page for the latest 2.1.2
release.
In apache camel they create the release notes quite early and then
collect the
I haven't been able to come up with a reason why Aegis would ever say
no to isWriteable or isReadable, but I'll study some more.
On Tue, Oct 14, 2008 at 10:52 AM, Sergey Beryozkin
[EMAIL PROTECTED] wrote:
Hi
Sounds good.
Have a look, say, at BinaryProvider unit test or at one of the atom
