[#MULE-4986] MessagePropertiesPropogationTestCase.testForcePropagatedPropertiesWithCxfTransport is either wrong or fails

Mule

MessagePropertiesPropogationTestCase.testForcePropagatedPropertiesWithCxfTransport is either wrong or fails

Created: 30/Jul/10 12:05 AM Updated: 30/Jul/10 02:48 PM

Component/s:

Transport: CXF / XFire

Affects Version/s:

3.0.0-M4

Fix Version/s:

None

Time Tracking:

Not Specified

Labels:
User impact:	Low
Similar Issues:

Description

« Hide

This test expects that after invoking a remote web service, the properties on an outbound message should be preserved back on the inbound message.

I would disagree with this. I you want these properties preserved, put them in the session.

Raising this issue as I've disabled the test.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 30/Jul/10 10:46 AM

I've come acrsoss the responseProperties list which gets a special treatment in Mule (for whatever reasons). Recent changes must have dropped this bit.

Session will NOT work, as the external service will drop the header with the serialized session, so I think this handling must be fixed (it's a simple implementation of a 'SmartProxy' pattern).

[ Permlink | « Hide ]

Dan Diephouse added a comment - 30/Jul/10 10:51 AM

Session properties do work. Check out the SessionPropertyChainingRouterTestCase.

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 30/Jul/10 02:48 PM

Wrong. In session test all of the services are controlled by Mule. And by default Mule will propagate the session contents header throughout. The failing test, though, is talking to an external web service, which doesn't preserve custom properties. responseProperties was the way to move those props along.