Dear Dan,
So how do you suggest we handle the scenario where SOAP message
consists of Chinese/German characters ? Can we expect this to be fixed in
next release of CXF? Or is there a quick fix for this at the server side?
Please advice.
anoopPrasad
dkulp wrote:
>
>
-4011
Will this affect the said functionality?
Kindly let me know your opinion on the above mentioned aspects.
regards
anoopPrasad
dkulp wrote:
>
>
> I THINK if you set the Message.ENCODING attribute on the message (for
> instance, in the RequestContext) to a string denoting the
Will update you on the progress :-)
<
Definitely still open for exploration. Explore away! :-)
Dan
>
--
View this message in context:
http://www.nabble.com/Application-Layer-Session-Management-for-WS-tp21868743p21970671.html
Sent from the cxf-dev mailing list archive at Nabble.com.
; something like what they have in Axis2. If yes kindly point me in
the right direction.
If not please let me know if we have any work in progress in this direction.
Thanks in advance.
regards
anoopPrasad
--
View this message in context:
http://www.nabble.com/Application-Layer-Session-Management
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 H
.com/fkieviet/entry/classloader_leaks_the_dreaded_java
If it's in the process memory space, that's probably a bug in either Jetty
(nio stuff it does) or in the JDK itself. Nothing we can do about either of
those.
If we locate the problem, we can try to fix it.
Thank you very much.
regard
onf | grep Memory
Memory size: 8192 Megabytes
Please help us identify the reason for this mem increase.
regards
anoopPrasad
bharath-5 wrote:
>
> Hi Hubert,
>
> Is the leak replicable? Is is that the memory was just high or it was a
> leak? Did you see an OOM?
> Will be of great h
