You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2017/03/27 16:34:42 UTC

[jira] [Resolved] (CXF-6529) Attachment configuration has no effect

     [ https://issues.apache.org/jira/browse/CXF-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-6529.
------------------------------
       Resolution: Not A Problem
    Fix Version/s: Invalid

This is as designed.  Those properties only are in effect when we have to break streaming and cache the attachments.  By default, CXF tries to stream attachments (and everything else) whenever possible and thus those properties are irrelevant.   There are several "events" that can cause having to cache the attachments and thats when these properties take effect.   Schema validation is one, SAAJ handlers are another, some aspects of security, querying the number of attachments in an interceptor, etc....  

> Attachment configuration has no effect
> --------------------------------------
>
>                 Key: CXF-6529
>                 URL: https://issues.apache.org/jira/browse/CXF-6529
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.16
>            Reporter: Michael Clay
>             Fix For: Invalid
>
>
> It seems like attachment-memory-threshold,attachment-max-size and attachment-directory configuration is ONLY effective if SCHEMA_VALIDATION_ENABLED is set to true which causes the JAXBAttachmentSchemaValidationHack to explicitly #hold( and cache) the request from ServletInputStream to file. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)