>>> error.
>>>
>>> Does anyone have any suggestions on what could be causing this
>>> truncation?
>>>
>>> Regards
>>> Brenda
>>>
>>
>> --
>> Daniel Kulp
>> dk...@apache.org
>> http://www.dankulp.com/blog
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/Large-SOAP-Attachment-getting-truncated-using-JAX-WS-tp27329816p27344645.html
Sent from the cxf-user mailing list archive at Nabble.com.
"Premature End Of
>> File"
>> error.
>>
>> Does anyone have any suggestions on what could be causing this
>> truncation?
>>
>> Regards
>> Brenda
>>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://old.nabble.com/Large-SOAP-Attachment-getting-truncated-using-JAX-WS-tp27329816p27344114.html
Sent from the cxf-user mailing list archive at Nabble.com.
Definitely try with CXF 2.2.6 if you are not already using 2.2.6. We've made
a lot of improvements in attachment handling in the last couple versions to
make them faster and more memory efficient.
If it's still an issue, is there any way a small test case could be provided.
I know we ha
If I remember correctly we had a problem with truncated request when
using the logging feature. If you use it you could try to deactivate the
feature.
Greetings
Christian
Am 26.01.2010 22:11, schrieb Brenda Coulson:
I have scoured the discussion forums, tried multiple attempts to understand
so, of a "Premature End Of File" error.
Does anyone have any suggestions on what could be causing this truncation?
Regards
Brenda
--
View this message in context:
http://old.nabble.com/Large-SOAP-Attachment-getting-truncated-using-JAX-WS-tp27329816p27329816.html
Sent from the cxf-us
