Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
This could be achieved by passing some state object (a map) to the function, which could be managed within the function. The state object could be created by Mirth before the first call, and destroyed by Mirth after the last call to the function. The object would only need to be maintained in memory for the duration of the batch splitting operation.
I have found a need for this, because when splitting, I need each output message to contain some of the same information from the inbound message. In these instances using router.RouteMessage from a filter or transform is undesirable.
Imported Issue. Original Details:
It is possible to maintain state using the globalChannelMap but because that map is global to the channel I think you can run into concurrency issues in some cases. The proposed solution limits the scope of the state object to the batch spliiter for that batch message, which mitigates any currency issues that could happen across messages on the channel.
Imported Comment. Original Details: