mediator

I have a proxy which accepts XML files with Base64 encoded files in it. For example the XML looks like: <message> <content>Hello World</content> <attachements> <attachement>*Base64 code here*</attachement> <attachement>*Base64 code here*</attachement> <attachement>*Base64 code here*</attachement> </attachements> </message> My Problem: I like to save the decoded files from the message into a folder of the filesystem of the server running the ESB. But how can I do this? If I encode a simple text like "Hello World" with Base64 I can decode it with an Script Mediator and Javascript, but how can I

This is not a question but rather an answer . I am quite new to wso2 ESB and wanted to make a test run implementing the split/gather EIP as part of a POC. I followed the examples I found and immediately got a working config that returned a single response. However to get all the responses back took quite some amount of time to figure out. Most given samples seemed to create the same unexpected result. I hope that if you run into the same kind of problem these lines will be helpfull to you. Setup I used the soapUI sample service (search operation) as service backend. I sent a combined message

As it says in the documentation of the DBLookup Mediator it only returns the first row of the query, the other results if they are, were ignored. I want to know if there is a "best way" to run a query (SELECT * FROM X) that return multiple records and then process them. Now a days we are doing that implementing axis2 services but there is another way using a combination of the mediators provided by wso2 esb to accomplished that requirement?? Thanks in advance. Santiago. Yes DBlookup mediator will not return multiple rows. You can use two alternatives. 1) Use WSO2 Data services Server to create

Can someone please help me sought out if I/Messenger class (and implementation) from MVVM light toolkit demonstrates usage of Event Aggregator Pattern or Mediator Pattern ? If someone proposes that it is following partially both the patterns then I request details of which part of implementation resembles which pattern to keep the answer valid. Ref: One comparison between the two pattern, which is absolutely interesting. I think the Messenger isn't a pure Event Aggregator nor a pure Mediator . If I where to choose between one of them I'd go for the Mediator . Lets do a little comparison.

I've been researching the difference between these two patterns. I understand that facade encapsulates access to a sub system and mediator encapsulates the interactions between components. I understand that sub system components are not aware of the facade, where as components are obviously aware of the mediator. I'm currently using a facade for encapsulating the method of retrieving configuration information, e.g. App.Config, user setting stored in SQL, Assembly info, etc, and a mediator for navigation between different windows forms. However, most sites point out that the mediator “adds

So far I have seen many solutions of the problem. The simplest one is, of course, to $emit an event in $rootScope as an event bus e.g. ( https://github.com/btilford/anti-patterns/blob/master/angular/Angular.md ) angular.module('myModule').directive('directiveA', function($rootScope) { return { link : function($scope, $element) { $element.on('click', function(event) { $rootScope.$emit('directiveA:clicked', event); }); } } }); angular.module('myModule').directive('directiveB', function() { return { link : function($scope, $element) { $rootScope.on('directiveA:clicked', function(event) { console