Re: [Architecture] [ESB] Guaranteed message delivery capability to the MSMP

Hi All. We faced an issue while using existing forward message processor as the failover message processor and decided to write separate failover message processor type to overcome this issue. *Problem.* When we send a message to the original message store and if store is not available, then

Re: [Architecture] Proposed ESB connector scenario - Integrating PipelineDeals with ZohoCRM, MailChimp, GoogleCalendar, Wunderlist, Dropbox, Mandrill and Billomat

Hi All, We have renamed following method names in Pipelinedeals connector as follows: listDocuments - Retrieve all documents listCalendarEntries - Retrieve all Calendar Events Thanks Regards Rasika -- View this message in context:

Re: [Architecture] [DAS] Changing the name of Message Console

+1 for data explorer which will also make sense for the people that were familiar with BAM Cassandra Explorer. Unless we are going to support other query languages like Siddhi or SQL it is good to keep the name spark console instead of query analyzer or query console. *Maninda Edirisooriya*

Re: [Architecture] [Dev] [GSoC-2015] Proposal2 : Siddhi Editor for WSO2 CEP

any update one this? Whats the approach we are taking now On Mon, Jul 6, 2015 at 4:34 PM, Tharindu Munasinghe munasinghethari...@gmail.com wrote: Yes , exactly they are not scalable models. There are several implementations I found but many of them doesn't provide context-sensitiveness for

Re: [Architecture] [GSoC] ESB - End-to-end Message Tracing Support

Hi Chanka, Can you please provide a status update on the project? On Tue, Jun 30, 2015 at 1:06 PM, Chanaka Sampath Cooray chanakasampat...@gmail.com wrote: Hi Kasun, Added to the doc. Thanks, On Tue, Jun 30, 2015 at 12:44 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi Chanaka, I think

Re: [Architecture] Workflow Implementation in IS 5.1.0

As Chathura describes, workflow templates are not easy to design. This is why we discussed some months ago a specialized language to ensure that template design is easy. Another alternative is to consider CMMN which has been designed to make skipping more easy... Maybe that's another subject to

Re: [Architecture] Workflow Implementation in IS 5.1.0

All, I am still not clear on how a customer would add A) a workflow template B) the corresponding implementation ( in BPEL or something else) So yes +1 to review and enhance/standardize across the platform as necessary. Isabelle. On Wednesday, July 15, 2015, Frank Leymann fr...@wso2.com wrote:

Re: [Architecture] Workflow Implementation in IS 5.1.0

If you want to introduce a new *workflow template* and a new *workflow* implementation - its a Java implementation of an interface. 1. *Workflow* - implementation independent abstract representation of the concrete workflow has two parts, *initializer* and the *executor*. 4. *Workflow Template *: