vember 2013 12:22
> To: Uwe Geisert
> Cc: dev@chemistry.apache.org
> Subject: RE: Streaming capability with WS binding
>
> Hi Uwe,
>
> The current code base (in trunk) does not do eager parsing.
>
>
> - Florian
>
>
>> Hi Florian,
>>
>> I
t: RE: Streaming capability with WS binding
Hi Uwe,
The current code base (in trunk) does not do eager parsing.
- Florian
> Hi Florian,
>
> I investigated the streaming issue a bit and found that
> "parseEagerly=true" in the JAX-WS annotation
>
> @Stream
configurable parameter as the
memoryThreshold already is?
Thanks
Uwe
-Original Message-
From: Florian Müller [mailto:f...@apache.org]
Sent: Mittwoch, 23. Oktober 2013 19:36
To: dev@chemistry.apache.org
Cc: Uwe Geisert
Subject: Re: Streaming capability with WS binding
Hi Uwe,
The abiliti
nal Message-
From: Florian Müller [mailto:f...@apache.org]
Sent: Mittwoch, 23. Oktober 2013 19:36
To: dev@chemistry.apache.org
Cc: Uwe Geisert
Subject: Re: Streaming capability with WS binding
Hi Uwe,
The abilities to stream, buffer in memory, buffer on disk, encrypt, and
dealing w
Hi Uwe,
The abilities to stream, buffer in memory, buffer on disk, encrypt, and
dealing with attachments in general are implementation details of the
JAX-WS framework and not covered by the JAX-WS specification.
OpenCMIS supports streaming if the Sun JAX-WS RI is used. The
WSConverter checks
Hi,
With Webservice-binding uploaded content gets loaded completely on the server
(either in memory or on disk, depending on the size, as specified in the
StreamingAttachment's memoryThreshold).
This issue has been discussed before in regards to encryption and
configurability of the threshold.