Re: [Architecture] [APIM] Admin REST API to check user role existence

t; <https://www.google.com/url?q=https://www.linkedin.com/in/meruja> > Medium: https://medium.com/@meruja > <http://wso2.com/signature> > > > On Mon, May 25, 2020 at 10:23 PM Frank Leymann wrote: > >> Dear Meruja, >> >> when would we return a 412

Re: [Architecture] [APIM] Admin REST API to check user role existence

Dear Meruja, when would we return a 412? Best regards, Frank Am Fr., 22. Mai 2020 um 15:42 Uhr schrieb Meruja Selvamanikkam < mer...@wso2.com>: > Hi all, > > We are in the process of implementing an API to get the scope list of a > particular user. > Following will be the notations of the

Re: [Architecture] [APIM] Admin REST API to check user role existence

Dear Malintha, my responses below Best regards, Frank Am Mi., 6. Mai 2020 um 08:40 Uhr schrieb Malintha Amarasinghe < malint...@wso2.com>: > Dear Frank, > > Thank you for looking into this. > It is my pleasure :-) > > On Tue, May 5, 2020 at 1:48 PM Frank L

Re: [Architecture] [APIM] Admin REST API to check user role existence

Dear Meruja, the URI of the second API (i.e. /me/roles/{roleName}) is really debatable: the intent of the */me* part of the URI seems to be to identify the logged-in user, and to me, such a user is a resource. I.e I assume that a user is represented in APIM as a resource (but I didn't check the

Re: [Architecture] REST API for Application Template Management

Dear Pamoda, - Why do you need both, limitWithoutDefaultQueryParam as well as limitQueryParam? Won't limitQueryParam do what we need? (same question for other parameters like offset etc) - Parameters like sortByQueryParam is not supported in the current version (according to the

Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Identity Provider Management

Hi Sathya, you support PATCH for the resource /identity-providers/{identity-provider-id} but for none of the other resources: any reason for this? Don't get me wrong, the less we support PATCH the better ;-) Best regards, Frank Am Sa., 2. Nov. 2019 um 06:24 Uhr schrieb Sathya Bandara : >

Re: [Architecture] [APIM-3.0] Store REST API to get all active tenants

Hi Dushan, I can't find the complete Swagger file. Would you please provide a link? Thanks! Best regards, Frank Am Mo., 12. Aug. 2019 um 16:22 Uhr schrieb Dushan Silva : > Hi all, > As per above suggestions i have updated the swagger. I have added state as > a query param. @Malintha

Re: [Architecture] [APIM][Monetization] Monetization Model For WSO2 API Manager

Would a discount pricing model make sense? E.g. after x requests you get a discount of y%? And what about adding a QoS aspect: if x requests failed within y duration, you get a discount of z% for D duration? Best regards, Frank Am Mi., 15. Mai 2019 um 08:21 Uhr schrieb Chamin Dias : > Hi

Re: [Architecture] HoneyPot APIs for API Manager - New Feature of APIM product

uld able to see this API also > (as a service) and they will try to invoke that API also. Then that > invocation will detect by us an anonymous invocation and provide an alert > to system admins. That's how to detect anonymous users arrived in APIM. > > Thank you & regards,

Re: [Architecture] HoneyPot APIs for API Manager - New Feature of APIM product

gt; anonymous attack. We are getting the headers (IP, if have access tokens) in > order to identify the attacker. Currently, we are implementing to detect > and alert this to the system admin. We hope to implement the blocking part > also in future time. > > Thank you & regards, >

Re: [Architecture] HoneyPot APIs for API Manager - New Feature of APIM product

In deed: very nice idea, valuable feature! Which attributes should be used to detect an attack? Best regards, Frank Am Do., 9. Mai 2019 um 11:09 Uhr schrieb Sanjeewa Malalgoda < sanje...@wso2.com>: > Tracing and logging problematic API calls definitely add value to product. > This is kind

Re: [Architecture] [APIM] Introduce API Product Concept

+1 , this is a useful feature (although we may invent another name for a group of APIs, because a single API today is subject to monetization, i.e. a "product"). Generalizing Chathura's question: do non-functional properties defined at the collection level (throttlling, security, pricing,...)

Re: [Architecture] [Intern Project] Graphical view for Exchanges, Bindings and Queues of MB4

Dear Ishara, I don't quite get want you want to achieve: a set of icons that represent the AMQP artifacts, and use them in the Ballerina modeling tool? Or do you want to graphically render a message flow, that is realized based on AMQP? Best regards, Frank Am Do., 24. Jan. 2019 um 15:13 Uhr

Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway

4 71 699 5861 > <http://wso2.com/signature> > > > On Fri, Dec 21, 2018 at 4:59 PM Frank Leymann wrote: > >> +1 - I am eager to see this :-) >> >> Are we running a performance comparison between HTTP 1.1 and HTTP/2? >> >> Best regards, >> Fran

Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway

+1 - I am eager to see this :-) Are we running a performance comparison between HTTP 1.1 and HTTP/2? Best regards, Frank Am Fr., 21. Dez. 2018 um 05:25 Uhr schrieb Nuwan Dias : > > > On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda > wrote: > >> Can you create document explaining this

Re: [Architecture] REST API versioning - which version to mandate in the URI scheme?

gt;>>> >>>>>>>> You could offer clients a URI only approach and header approach in >>>>>>>> parallel like this: >>>>>>>> >>>>>>>> /someresource/v1/thisandthat -> default version, always latest

Re: [Architecture] [APIM][C5] - Definining Endpoint for Resource from Rest API

t; Hi All > > On Tue, Dec 20, 2016 at 9:48 PM, Frank Leymann <fr...@wso2.com> wrote: > >> If an API Resource or endpoint is nothing stand-alone, i.e. if it needs >> an API Definition and can't live without it, it should be nested under API >> Definition. Thus, "+1! &g

Re: [Architecture] [APIM][C5] - Definining Endpoint for Resource from Rest API

If an API Resource or endpoint is nothing stand-alone, i.e. if it needs an API Definition and can't live without it, it should be nested under API Definition. Thus, "+1! Furthermore, I took a look at [1]. In line 167, a HEAD method is defined. A HEAD on a certain URI returns the very same than

Re: [Architecture] NextGen Tooling - Tool Palette

regards, Frank 2016-09-04 4:31 GMT+02:00 Imesh Gunaratne <im...@wso2.com>: > Hi Frank, > > On Sat, Sep 3, 2016 at 8:35 PM, Frank Leymann <fr...@wso2.com> wrote: > >> Let me even emphasize what Chathura wrote: users will be really annoyed >> if we don't preser

Re: [Architecture] NextGen Tooling - Tool Palette

Let me even emphasize what Chathura wrote: users will be really annoyed if we don't preserve the layout/rendering of a diagram. It will be a show-stopper for using the tool Best regards, Frank 2016-08-31 6:01 GMT+02:00 Chathura Ekanayake : > Hi Susinda / Imesh, > > If

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

gt; > On Mon, Jun 20, 2016 at 10:48 AM, Nandika Jayawardana <nand...@wso2.com> > wrote: > >> Hi Frank, >> >> Not accepting a change in the substitute when there is a cyclic situation >> is the options we decided as well. >> >> Regards >> Nand

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

on starts in a future time(not just after > changing the substitute user), we do not have the option of rejecting the > substitution request. In such a scenario, we will have to make his tasks > unclaimed! > > Regards, > Vinod > On Jun 16, 2016 2:28 AM, "Frank Leymann"

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

n we can overcome the current >>> limitations of user tasks. >>> >>> Regards >>> Nandika >>> >>> On Wed, Jun 8, 2016 at 7:18 PM, Milinda Perera <milin...@wso2.com> >>> wrote: >>> >>>> >>>&

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

WS-HumanTask. It has only > Created, Claimed and Completed states. > > Regards, > Vinod > > On Wed, Jun 8, 2016 at 2:52 PM, Frank Leymann <fr...@wso2.com> wrote: > >> Dear Vinod, >> >> BPMN 2.0 explicitly refers to WS-HumanTask as implementat

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

Vinod, re-assignment must consider the state of the task. In your scenario, the task that B is working on is inProgress (BPMN / HumanTask terminology = "active/workedOn" in informal terminology also used in BPMN spec) and will not (!) be re-assigned. Note that "claimed" means that a human being

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

Dear Vinod, BPMN 2.0 explicitly refers to WS-HumanTask as implementation of a User Task (see pp 166 ff) - although they say that there are many potential different implementations, HumanTask is preferred (...and I co-authored these sections, summarizing the position of the group ;-)). Thus, BPMN

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

I refer to the states defined in the HumanTask spec: http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cd-06.pdf Section 4.10 defines these states - "claimed" is not what the standard defines because different implementations had slightly different semantics, thus, we renamed the states

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

Fantastic! Thanks! Best regards, Frank 2016-06-02 5:21 GMT+02:00 Vinod Kavinda <vi...@wso2.com>: > Hi Frank, > Yes, the determining of users as substitutes will be a transitive process. > > Regards, > Vinod > > On Wed, Jun 1, 2016 at 10:48 PM, Frank Leymann <

Re: [Architecture] BPMN - Bulk Task Reassignment, Substitution feature

Hi Vinod, great that you are implementing it! As described in [1], substitution processing is transitive. Your diagram doesn't explicitly depict this transitive processing: are you considering this but the diagram leaves that out for clarity? [1]

Re: [Architecture] RESTFul API for App Manager - Design discussion

Sanjeewa (or Prabath) may have guidance on this... Best regards, Frank 2016-04-27 11:11 GMT+02:00 Thilini Shanika : > + Frank > > On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika > wrote: > >> Hi, >> >> We have a little concern regarding the permission

Re: [Architecture] [Dev] [REST APIs][Analytics] GET request with a payload

il > we do a major release. Of course the new changes in these REST APIs and new > REST APIs will be created adhering to those REST API Guidelines. > > On Fri, Apr 15, 2016 at 10:54 PM, Frank Leymann <fr...@wso2.com> wrote: > >> We built a REST API Guideline docume

Re: [Architecture] [Dev] [REST APIs][Analytics] GET request with a payload

We built a REST API Guideline document a few weeks ago. Do you (Gimantha) see that? Its purpose is to help in designing REST APIs. If you think it would be helpful for you and your team, we can set up a call on this Best regards, Frank 2016-04-15 16:00 GMT+02:00 Manuranga Perera

Re: [Architecture] [C5] Artifact deployment coordination support for C5

Sorry for jumping in so late in the thread: is technology like HEAT/HOT (OpenStack) or TOSCA (OASIS) too encompassing? I am happy to provide on overview of their features... I am not suggesting to use the corresponding implementations (they have their pros/cons) but we may learn from the

Re: [Architecture] Circuit Breaker Pattern for MSF4J

e lazy developers love to >>>> Google search for code segments, e.g. JDBC connection example, and then >>>> copy, paste and modify those segments. What I have been trying to do with >>>> the series of blogposts is to make available such code segments develo

Re: [Architecture] Circuit Breaker Pattern for MSF4J

Yes, all the stability patterns (that Nygard describes, the circuit breaker being just one of them) is not associated with microservices, but applies to all distributed applications. In fact, Nygard's book has been published in 2007, lng before the microservice discussion came up ;-) Applying

Re: [Architecture] Data Isolation level for Data from APIM and IoT? Tenant vs. User

Sorry for jumping into the discussion late (or even too late). I try to understand the discussion by drawing analogies to DBMS - maybe that's wrong and I miss the point... If I am right, what you decided in the meeting is fully in line with what DBMS are doing :-) In Srinath's summary, list item

Re: [Architecture] Session Affinity Alternatives

ever, AFAIK session replication or pressitance that is in WSO2 AS was > rarely used. ( Azeez, please correct me if I am wrong). > > --Srinath > > On Thu, Mar 17, 2016 at 11:42 PM, Frank Leymann <fr...@wso2.com> wrote: > >> Sorry for jumping in late in the discussion >> &

Re: [Architecture] Session Affinity Alternatives

Sorry for jumping in late in the discussion Session affinity in general is bad (scalability, HA) - I guess that's what we all agree on. But in certain scenarios, sticky sessions may be fine. Thus, what is the underlying scenario in the case we discuss? As far as I understand, persisting

Re: [Architecture] Circuit Breaker Pattern for MSF4J

I do have a more general question: what justifies the focus on the "circuit breaker" pattern at all? It is just one patter to solve recurring problems with stability, i.e. other patterns are there too that are important (e.g. "timeout" - see Michael Nygard's nice book). Thus, what are the

Re: [Architecture] [BPMN] Implementing correlation support for BPMN Rest API

Thanks a lot, Firzhan, for letting me know! I think that's the right way to go :-) Best regards, Frank 2015-12-22 14:11 GMT+01:00 Firzhan Naqash : > Hi Frank, > > After having discussion with Nandika, Chathura and Amal, it was decided > not to support multiple receiving

Re: [Architecture] [BPMN] Implementing correlation support for BPMN Rest API

The process model you have drawn enables multiple receiving message events in parallel. According to the BPMN 2.0 spec this is not allowed for key-based correlation (i.e. the correlation mechanism similar to BPEL correlation sets); but it is allowed for predicate based correlation (often used in

Re: [Architecture] API Manager REST API with tier grouping feature

> Thanks. > > > On Tue, Dec 1, 2015 at 5:32 PM, Frank Leymann <fr...@wso2.com> wrote: > >> Just to double-check: but we still have a POST /tiers to add a new tier >> to the collection, right? >> >> >> Best regards, >> Frank >> >> 20

Re: [Architecture] Forceful queue/topic subscription deletion for Message Broker

+1 I would even say stronger "...we MUST give a way..." Best regards, Frank 2015-12-03 11:01 GMT+01:00 Srinath Perera : > If the user must go to the node where subscription is made to disconnect > the subscription, we might need to give a way for a user to find which node >

Re: [Architecture] API Manager REST API with tier grouping feature

Just to double-check: but we still have a POST /tiers to add a new tier to the collection, right? Best regards, Frank 2015-12-01 11:50 GMT+01:00 Nuwan Dias : > I think the group param should be mandatory. Therefore there will not be a > GET /tiers, but instead a GET

Re: [Architecture] Specifying the tenant domain in the request URI for the cross-tenant scenarois in API Manager REST API

e transport header and part of API. >> >> I think malintha already implemented this for some resources which >> requires requested tenant. He may provide more information. >> >> Thanks >> sanjeewa. >> >> sent from my phone >> On Nov 22, 2015 7:14 PM,

Re: [Architecture] Specifying the tenant domain in the request URI for the cross-tenant scenarois in API Manager REST API

rt of >>> context. So application url remain as it is and current logged tenant will >>> identified using authentication details client send(we start tenant flow >>> based on logged in user). >>> If need we can make tenant name query parameter in url. >>> Reques

Re: [Architecture] Specifying the tenant domain in the request URI for the cross-tenant scenarois in API Manager REST API

Dear all, let me try to understand: A user (us...@wso2.com) wants to access a resource created by a certain tenant (cloud.com) - correct? The tenant created the resource and we decided to make the tenant-id part of the context of the resource's URL. Thus, the user who wants to access the

Re: [Architecture] API Manager REST API separation for store and publisher.

A GET on a resource returns *the* resource. All that can vary is its requested representation (i.e. as JSON, XML,... rendering). I.e. if the GET in Store and the GET in Publisher return different resources (i.e. different data structures independent from their rendering) we should have two

Re: [Architecture] IS Workflow Implementation - Issues in AddUser Workflow

mentioned in my previous mail, we need a way so that an admin user can see list of people with those who are still in workflows and not accepted. Thanks On Wed, Jul 22, 2015 at 5:37 PM, Frank Leymann fr...@wso2.com wrote: Dear Chamila, in summary, you are implementing a pessimistic offline lock

Re: [Architecture] IS Workflow Implementation - Issues in AddUser Workflow

Dear Chamila, in summary, you are implementing a pessimistic offline lock, right? http://martinfowler.com/eaaCatalog/pessimisticOfflineLock.html Best regards, Frank 2015-07-22 7:23 GMT+02:00 Chamila Wijayarathna cham...@wso2.com: Hi all, Currently we are in the process of implementing

Re: [Architecture] Workflow Implementation in IS 5.1.0

with Chathura, we are creating a parameterized BPEL workflow and parameters are picked from the user through the template (in IS). So the same BPEL workflow will find different execution paths based on the template... Thanks regards, -Prabath On Wed, Jul 15, 2015 at 6:02 AM, Frank Leymann fr

Re: [Architecture] Workflow Implementation in IS 5.1.0

, -Prabath On Wed, Jul 15, 2015 at 6:02 AM, Frank Leymann fr...@wso2.com wrote: 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

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

Re: [Architecture] Workflow Implementation in IS 5.1.0

+1 Whatever we come up with, it must be usable across out product set... Best regards, Frank 2015-07-14 22:12 GMT+02:00 Prabath Siriwardena prab...@wso2.com: BTW yes - lets have a discussion on this again - because this is not just IS thing - and can be used by any other product which needs

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] Generic workflow executor across the platform

end. We will use some BPELs as templates and get the inputs from a form to customize it. On Sat, Apr 11, 2015 at 8:02 PM, Frank Leymann fr...@wso2.com wrote: Hi Pulasthi, when you have users without BPEL knowledge in mind, you assume that these users have programming skills, correct? I.e

Re: [Architecture] Operations Center RestAPI

-id}/commands/{command-id} Thank you. Regards, Chaya Chaya Sandamali Software Engineering Intern WSo2 Inc Mobile: +94714905772 LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/ On Wed, Mar 18, 2015 at 4:48 PM, Frank Leymann fr...@wso2.com wrote: Dear Chaya

Re: [Architecture] Generic workflow support

Hi Pulasthi, based on what information will the Workflow Manager decide which Workflow Executor to use? Best regards, Frank 2015-04-04 14:01 GMT+02:00 Pulasthi Mahawithana pulast...@wso2.com: Hi, Following is the architecture of the workflow support framework. This was initially planned

Re: [Architecture] Generic workflow executor across the platform

a workflow process and deploy it at BPS (for the users without BPEL knowlege). The work for that is in progress and we will update with the details soon. [1] [Architecture] Generic workflow support On Thu, Apr 2, 2015 at 8:31 PM, Frank Leymann fr...@wso2.com wrote: Hi Pulasthi, hi Tanja

Re: [Architecture] Generic workflow executor across the platform

Hi Pulasthi, hi Tanja, can you provide a consolidated architecture figure, please? Can you also position in your architecture BPS? I assume the requirements you address by your architecture is the ability to create an on-ramp workflow for ES, AM,... in a fast way, correct? Thanks! Best

Re: [Architecture] RFC: RESTFul API for API Manager

mentioned these controlled-resources are always lead to discussion. Do you have any comments on the usage of '-' instead of camel case ? On Tue, Mar 31, 2015 at 10:51 PM, Frank Leymann fr...@wso2.com wrote: Hi Jo, hi Manu, how to cope with actions that cannot be mapped onto the CRUD methods

Re: [Architecture] RFC: RESTFul API for API Manager

/restful-apim/ On Sat, Mar 28, 2015 at 12:47 AM, Frank Leymann fr...@wso2.com wrote: Hi Jo, again, thanks for your work: we'll get a nice RESTful API :-) In the Richardson maturity model we'll get to level 2 (not level 3 because we are leaving out HATEOS - which is something that is not used

Re: [Architecture] RFC: RESTFul API for API Manager

://hevayo.github.io/restful-apim/ On Sat, Mar 28, 2015 at 12:47 AM, Frank Leymann fr...@wso2.com wrote: Hi Jo, again, thanks for your work: we'll get a nice RESTful API :-) In the Richardson maturity model we'll get to level 2 (not level 3 because we are leaving out HATEOS - which is something

Re: [Architecture] Operations Center RestAPI

, Frank Leymann fr...@wso2.com wrote: Dear Chaya, is there a pointer to the REST API? I would be interested in its URIs, HTTP methods used on each URI, header fields supported, status codes returned... Thanks! Best regards, Frank 2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2

Re: [Architecture] RFC: RESTFul API for API Manager

://github.com/hevayo/restful-apim/blob/master/apim.yaml#L18-L19 On Wed, Mar 25, 2015 at 3:51 PM, Frank Leymann fr...@wso2.com wrote: Hi Jo, nice piece of work! What is still needed is a description of the header fields for both, the requests and APIs. Best regards, Frank 2015-03-24 17:34 GMT

Re: [Architecture] RFC: RESTFul API for API Manager

at 3:51 PM, Frank Leymann fr...@wso2.com wrote: Hi Jo, nice piece of work! What is still needed is a description of the header fields for both, the requests and APIs. Best regards, Frank 2015-03-24 17:34 GMT+01:00 Joseph Fonseka jos...@wso2.com: Hi All We are planing to implement

Re: [Architecture] Operations Center RestAPI

Dear Chaya, is there a pointer to the REST API? I would be interested in its URIs, HTTP methods used on each URI, header fields supported, status codes returned... Thanks! Best regards, Frank 2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com: Hi all, After the last review,we came

Re: [Architecture] [Dev] Improving Impact Analysis Feature on G-Reg

together, these features alone will make G-Reg 10-times more usable that where it stands today in terms of Asset Governance. Thanks, Senaka. On Sun, Feb 22, 2015 at 5:00 PM, Frank Leymann fr...@wso2.com wrote: HI Jerad, thanks, the gif was helpful :-) Very nice tool! Coloring nodes

Re: [Architecture] [Dev] Improving Impact Analysis Feature on G-Reg

/ On Sun, Feb 22, 2015 at 6:00 PM, Frank Leymann fr...@wso2.com wrote: HI Jerad, thanks, the gif was helpful :-) Very nice tool! Coloring nodes is optional (I would even argue: not needed). But coloring relations will in fact improve comprehension of the user. See for example when you select

Re: [Architecture] [Dev] Improving Impact Analysis Feature on G-Reg

HI Jerad, thanks, the gif was helpful :-) Very nice tool! Coloring nodes is optional (I would even argue: not needed). But coloring relations will in fact improve comprehension of the user. See for example when you select in your gif a subset of relationship types: it is still unclear which

Re: [Architecture] BAM 3.0 REST APIs for AnalyticsDataService / Indexing / Search

Hi Gimantha, it depends on the scenario: if you want to check existence of resource it's fine to use a GET on this resource and receive a 404 Not Found. But the subtlety is that Not Found according to HTTP is statement in time: you cannot infer that the resource does not exist, all that 404

Re: [Architecture] Process center- Multiple predecessor/successor support for chevron diagram editor

to be solved (by automatic layouting,e.g. +1 ,will include it . Thanks Regards, Himasha On Fri, Jan 16, 2015 at 3:54 PM, Frank Leymann fr...@wso2.com wrote: Hi Himasha, great progress! Thanks! :-))) A few comments/questions: 1. Can we add arrow heads to the lines between

Re: [Architecture] Process center- Multiple predecessor/successor support for chevron diagram editor

previous column. Regards, Chathura On Thu, Dec 11, 2014 at 11:50 PM, Frank Leymann fr...@wso2.com wrote: Hi Himasha, very good idea :-)Let me suggest a little variation: People modeling Chevron Diagrams are not really used to use arrows to connect the individual chevrons to indicate

Re: [Architecture] Process center- Multiple predecessor/successor support for chevron diagram editor

with all chevrons in its previous column. Regards, Chathura On Thu, Dec 11, 2014 at 11:50 PM, Frank Leymann fr...@wso2.com wrote: Hi Himasha, very good idea :-)Let me suggest a little variation: People modeling Chevron Diagrams are not really used to use arrows to connect

Re: [Architecture] Process center- Multiple predecessor/successor support for chevron diagram editor

Hi Himasha, very good idea :-)Let me suggest a little variation: People modeling Chevron Diagrams are not really used to use arrows to connect the individual chevrons to indicate (control or data) flow. The flow is defined by the orientation of the diagram (i.e. horizontal or vertical). This

Re: [Architecture] [Process center] Support for executable process models

Hi Chathura, ​what is the semantics of the deployment URL (second bullet): is this the endpoint where a BPEL archive can be deployed? Or is this the URL of an archive that contains all the artifacts to create a BPEL engine where I can deploy and execute the BPEL file? I suspect the first

Re: [Architecture] Chevron diagram editor/viewer for the Process Store

/0B2gZ09XLMRjKS0czei1OQWtqekU/view?usp=sharing [2] individual_chevron_properties https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKcjBaOW5EcUI0Y28/view?usp=sharing Thanks Regards, Himasha On Sun, Nov 30, 2014 at 10:19 PM, Frank Leymann fr...@wso2.com wrote: Hi Himasha, please allow for a few

Re: [Architecture] [Process center] Support for executable process models

+1 Best regards, Frank 2014-12-04 4:40 GMT+01:00 Chathura Ekanayake chath...@wso2.com: Hi Chinthana, Process center is not used to interact with the BPS runtime or HT runtime. Instead, end users use it to search/discover available processes and to execute them if possible. If a user wants

Re: [Architecture] [Process center] Support for executable process models

Please add me to the tbd thread on processes and event streams :-) Best regards, Frank 2014-12-03 14:43 GMT+01:00 Chathura Ekanayake chath...@wso2.com: Hi Srinath, Yes, if a process is already deployed, it can just store the deployment URL. An example scenario would be: An employee

Re: [Architecture] Chevron diagram editor/viewer for the Process Store

Hi Himasha, please allow for a few questions/comments: 1. create_chevron: 1. Is the list of properties of a chevron fixed? Or does add properties mean that I can add more properties? I suspect that the list of property types of a chevron is pre-defined... 2. What is

[Architecture] Machine Processable Metadata and GUI Generation

Here is the link to the technology called OSCL I was mentioning: http://open-services.net/resources/tutorials/oslc-primer/what-is-oslc/ Best regards, Frank ___ Architecture mailing list Architecture@wso2.org

Re: [Architecture] RFC: Doing Bulk Events Updates to HDFS instead of Cassandra

Hi Srinath, I assume the scenarios you intend to support by such file manipulations do not require typical database functionality like concurrent access, atomicity of sets of manipulations, random and selective access (aka queries) etc.. Am I right? Best regards, Frank 2014-11-05 3:56

Re: [Architecture] Chevron diagram editor/viewer for the Process Store

Hi Himasha, I don't understand what you mean by deriving predecessor/successor relationships for the entire diagram: does that mean that you derive the relationships for all chevrons of a diagram at once, i.e. that you apply your second bullet iteratively? Will the position on the canvas of each

Re: [Architecture] WSO2 MB Proposed RDBMS Design

Prabath, I agree that triggers make comprehending code a bit more difficult. But triggers are a mechanism to achieve active database features, something that is very difficult to get without triggers. Thus, I would not say that they should not be used. I don't understand the statement that

Re: [Architecture] WSO2 MB Proposed RDBMS Design

This is true in general: even a simple statement like SELECT behaves a bit differently in different RDBMS implementations. I.e. minor differences in SQL statements is not restricted to triggers, however we use RDBMS... Best regards, Frank 2014-09-12 10:24 GMT+02:00 Sumedha Rubasinghe

Re: [Architecture] WSO2 MB Proposed RDBMS Design

stored procedures provide heavy advantages, we have avoided using them due to the complexity of managing them for different databases. On Sep 14, 2014 4:19 PM, Frank Leymann fr...@wso2.com wrote: This is true in general: even a simple statement like SELECT behaves a bit differently

Re: [Architecture] RFC: Could we support Hive executions on top of Hazelcast?

Hi Srinath, another minor point that came to me: Google announced recently the successor of MapReduce, called Google Cloud Dataflow ( http://googlecloudplatform.blogspot.in/2014/06/reimagining-developer-productivity-and-data-analytics-in-the-cloud-news-from-google-io.html). Because you are

Re: [Architecture] RFC: Could we support Hive executions on top of Hazelcast?

Sorry - my comment is on the wrong thread :-( Best regards, Frank 2014-09-07 15:26 GMT+02:00 Frank Leymann fr...@wso2.com: Hi Srinath, another minor point that came to me: Google announced recently the successor of MapReduce, called Google Cloud Dataflow ( http