Issue Details (XML | Word | Printable)

Key: MULE-3340
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Dirk Olmes
Reporter: Andrew Perepelytsya
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

There's no vm:transaction element in the VM schema

Created: 14/May/08 03:12 PM   Updated: 18/Jun/08 05:07 AM
Component/s: Core: Configuration
Affects Version/s: 2.0.1
Fix Version/s: 2.0 ITR3, 2.0.2

Time Tracking:
Original Estimate: 3 hours
Original Estimate - 3 hours
Remaining Estimate: 0 minutes
Time Spent - 2 hours
Time Spent: 2 hours
Time Spent - 2 hours Time Not Required

Issue Links:
Duplicate
 
Related
 

Labels:
User impact: Medium
Effort points: 0.5


 Description  « Hide
I was surprised to have found no way to configure a vm transaction because of schema limitations. Currently, the only way to do it is resorting to a custom tx, which is what it was called to replace:
<vm:inbound-endpoint path="bridge">
                    <custom-transaction action="BEGIN_OR_JOIN" factory-class="org.mule.transport.vm.VMTransactionFactory"/>
                </vm:inbound-endpoint>

There must be a vm:transaction element.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order