[CXF-7676] TCK: An Entity OutputStream is not set before ClientRequestFilterInterceptor.handleMessage() processes a user's ClientRequestFilter which modifies the EntityStream via ClientRequestContext.setEntityStream()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.2.3, 3.2.4
• Component/s: JAX-RS

Environment

all versions, any environment

• Estimated Complexity: Moderate
• Assignee: Daniel Kulp
• Reporter: Adam Anderson
• Created: 12/Mar/18 17:09
• Updated: 17/Apr/18 00:57
• Resolved: 16/Mar/18 18:08

Description

CXF is failing a test in both the JAXRS 2.0 and 2.1 TCKs where a user creates a ClientRequestFilter which wraps the EntityStream in the filter() method via ClientRequestContext.setEntityStream().

CXF uses Phases to order the interceptors in the PhaseInterceptorChain. http://cxf.apache.org/docs/interceptors.html

A customer's client filter code gets executed in ClientRequestFilterInterceptor.handleMessage() during the PRE_LOGICAL phase of the outgoing chain.
We don't actually create the entity output stream until HTTPConduit.prepare() which is called by MessageSenderInterceptor.handleMessage() during the PREPARE_SEND phase of the outgoing chain.

As a result, any interaction/modification of the entity stream by the user gets overwritten.

Issue Links

• links to: GitHub Pull Request #390