Skip to content

Construct StringWriter instances with appropriate initial size #25789

@jhoeller

Description

@jhoeller

Our StringWriter usage in several message converters and in FileCopyUtils effectively initializes a StringBuffer with a default initial capacity of 16. Since we use an initial size of 1024 for messages and 4096 for files in case of a byte array, we should align there for our equivalent StringWriter code paths.

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)in: messagingIssues in messaging modules (jms, messaging)status: backportedAn issue that has been backported to maintenance branches

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions