[#MULE-2038] Transformers are not persisted when using VM queueing

Mule

Transformers are not persisted when using VM queueing

Created: 16/Jul/07 08:18 PM Updated: 01/Feb/08 09:12 AM

Component/s:

Core: Transformers

Affects Version/s:

1.4.1

Fix Version/s:

1.4.2

Time Tracking:

Not Specified

Issue Links:

Related

This issue relates to:

~~MULE-2961~~ Restoring persisted events does not reattach event to valid UMOSession

Labels:
User impact:	Medium

Description

« Hide

http://www.nabble.com/-Fwd%3A-Unknown-behavior-of-transformer-on-outbound-router-%2B-vmQueue-with-queueEvents%3Dtrue--t3961722.html#a11243021

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 16/Jul/07 09:10 PM

http://fisheye.codehaus.org/changelog/mule/?cs=7534

[ Permlink | « Hide ]

Andrew Cooke added a comment - 17/Jul/07 07:33 AM

How is this code going to work on 2.0? (I'm just curious - I wondered what the issue was, looked at the code, and saw MuleManager).

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 17/Jul/07 08:56 AM

Read the thread. The issue was with persisting events when using VM queueing (persistent), transformers were lost. Not so for non-persistent messaging.

There won't be a problem with MuleManager, it's still possible to get a hold of managementContext statically from any place in Mule 2.x via the RegistryFacade&Context.

[ Permlink | « Hide ]

Holger Hoffstaette added a comment - 01/Feb/08 09:07 AM

sorry, reopened by mistake