Hi All
Here's the list of changes discussed during our last meeting;
1. A way to create a new connection if no connections are available
2. Set properties to be renamed to *Set Parameters*
3. Example to be corrected (renaming spreadsheet extension from *doc* to
*gsheet*)
4. Multiple connections
Hi All,
According to the discussion we had during last week, I have implemented the
recipe executor as a carbon component. Currently it will use the Task
interface and once we integrate the Task Server with the ESB, we will use
that for the implementation. Now we have a CAR file which contains
Hi all,
We had a detailed discussion on the architecture and the design of the new
'Recipe' concepts for ESB. This is a summary of what we have discussed.
*Recipe* : The concept behind Recipe is about providing high level
abstraction for connectors interactions. The well known and commonly
What would user experience be like? Surely, users will not be editing XML
files, I presume.
Azeez
On Tue, Mar 4, 2014 at 10:55 AM, Kasun Indrasiri ka...@wso2.com wrote:
Hi all,
We had a detailed discussion on the architecture and the design of the new
'Recipe' concepts for ESB. This is a
I love this idea. What about trigger instead of executor? Also, is
recipe the right word? Would adapter be more suitable?
On Mon, Mar 3, 2014 at 9:28 PM, Afkham Azeez az...@wso2.com wrote:
What would user experience be like? Surely, users will not be editing XML
files, I presume.
Azeez
