[
https://issues.apache.org/jira/browse/CXF-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201432#comment-13201432
]
Alessio Soldano commented on CXF-4030:
--------------------------------------
AFAICS the use of CachedOutputStream for dealing with multipart/related
messages and attachments in general is already going through the
CachedOutputStream(long threshold) constructor (see for instance the
org.apache.cxf.attachment.AttachmentDeserializer and its ATTACHMENT_* constants
for controlling threshold, maxsize, etc. through message context properties).
Is that enough? Or you need to control these settings in different scenarios?
> externalize configuration of org.apache.cxf.io.CachedOutputStream.Threshold
> ---------------------------------------------------------------------------
>
> Key: CXF-4030
> URL: https://issues.apache.org/jira/browse/CXF-4030
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Environment: N/A
> Reporter: David J. M. Karlsen
> Assignee: Alessio Soldano
>
> Seems like the threshold can only be set as a system property:
> http://www.java2s.com/Open-Source/Java-Document/Web-Services-apache-cxf-2.2.6/common/org/apache/cxf/io/CachedOutputStream.java.htm
> I'd like to configure the threshold individually for applications in the same
> container - so it would be preferable to configure this through the endpoint
> and/or bus.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
