/www.linkedin.com/in/meruja
> <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,
>>
>&
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 ne
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
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 c
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
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 :
> H
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 Amarasi
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 all
ey could 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 &
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,
>
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 of
+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,...) o
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
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
+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 fea
;>>>>>>> Assuming these policies are in place:
>>>>>>>> P1: minor versions guarantee backward compatibility
>>>>>>>> P2: major version can break backward compatibility
>>>>>>>>
>>>>>>>> Y
, Dec 20, 2016 at 9:48 PM, Frank Leymann 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!
>>
>> Furthermore, I took
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 a
We need to discuss this more carefully.
The real question is: *do we want to make it easy for us, or do we want to
make it easy for our customers? *I think that we should strive for APIs
that serve our customers as simple as possible. And this means that clients
must not break.
Nearly all
know
layout info.
Best regards,
Frank
2016-09-04 4:31 GMT+02:00 Imesh Gunaratne :
> Hi Frank,
>
> On Sat, Sep 3, 2016 at 8:35 PM, Frank Leymann wrote:
>
>> Let me even emphasize what Chathura wrote: users will be really annoyed
>> if we don't preserve the layout/renderi
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 positioning informatio
a good solution for us
> since we want to allow our java API to be used by other components.
>
> 3. Above lead us to think the cache should be maintain at the java API
> (impl) layer to track updates which can be read by REST APIs to generate
> ETags and serve conditional statements.
Sanjeewa,
yes, Level 3 of the Richardson Maturity Model is about HATEOAS. And we
agreed to not support HATEOAS because there are no accepted best practices
around that, especially, how clients would make effective use of it.
Level 2 is about proper use of HTTP methods, which *includes* use of
app
un 20, 2016 at 10:48 AM, Nandika Jayawardana
> wrote:
>
>> Hi Frank,
>>
>> Not accepting a change in the substitute when there is a cyclic situation
>> is the options we decided as well.
>>
>> Regards
>> Nandika
>>
>> On Fri, J
n 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"
gt;> Vinod
>>
>> On Wed, Jun 8, 2016 at 10:03 PM, Nandika Jayawardana
>> wrote:
>>
>>> Yes, Once the task engine refactoring is complete, we can integrate our
>>> own task implementation with activiti . Then we can overcome the current
>>>
ask. It has only
> Created, Claimed and Completed states.
>
> Regards,
> Vinod
>
> On Wed, Jun 8, 2016 at 2:52 PM, Frank Leymann wrote:
>
>> Dear Vinod,
>>
>> BPMN 2.0 explicitly refers to WS-HumanTask as implementation of a User
>> Task (see pp 166 ff) -
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 sa
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 2
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
Fantastic! Thanks!
Best regards,
Frank
2016-06-02 5:21 GMT+02:00 Vinod Kavinda :
> 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 wrote:
>
>> Hi V
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] https://mail.google.com/mail/u/0/#sent/154edd36f
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 check in OAuth secured
>> APIs in APPM.
>
ease. 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 wrote:
>
>> We built a REST API Guideline document a few weeks ago. Do you
>> (Gimantha) see tha
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 :
> 1) S
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 concepts
ode 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 developers
>>>> could readily use. Since this post and mail thread has genera
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
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
ameter has changed, framework (e.g.
>>> Servelt runtime, or MSS framework) will write the update to the disk
>>> asynchronsly.
>>>
>>> Since we are a middleware platform, impact of losing a session depends
>>> on the kind of the application end use
ication 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 wrote:
>
>> Sorry for jumping in late in the discussion
>>
>> Session affinity in general i
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 sess
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 criteria
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 message events in paral
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 co
:
> Hi Nuwan,
>
> Thanks for the clarification.
>
> Hi Frank,
>
> Yes, would that need to be changed for POST /tiers/{tier-level}? Or shall
> we keep the previous one (/tiers ) only for POST and identify the tier
> level from the request body?
>
> Thanks.
>
>
+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
> has what subscriptio
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 /tiers/{level} only.
>
> Th
t 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.
>>> Requested tenant can be transport header and part of API
t; 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, "Frank Leymann" wrote:
>>
+1
I love to use YAML because of its simplicity, although I hate to give up
schema validation that XSD brings to the table. But (as far as I know) you
can't have both.
Best regards,
Frank
2015-11-26 7:14 GMT+01:00 Srinath Perera :
> Hi Azeez,
>
> Way I see it we should eventually move everyt
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 tenant
Hi Sanjeewa,
I assume Store and Publisher share the same database although they will
offer different APIs, correct? In that case, a common data model is the
preferred way.
Best regards,
Frank
2015-10-14 8:25 GMT+02:00 Sanjeewa Malalgoda :
> Thanks Frank ,Amila, Harshana, Jo, Dhanuka for your
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 differen
tioned 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 wrote:
>
>> Dear Chamila,
>>
>> in summary, you a
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 :
> Hi all,
>
> Currently we are in the process of implementing Workflow support
expecting the users to complete tasks (e.g. approval steps)
>>>> using the BPS Human Task web app? Or are we providing an integrated human
>>>> task UI in the IS management console?
>>>>
>>>> Scenario C:
>>>> Are there any other steps invo
+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 :
> 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 to have
> work
>
> 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, Jul
s we discussed 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
, if those are mandatory.
>>
>> Regards,
>> Chathura
>>
>>
>>
>> On Wed, Jul 15, 2015 at 9:40 PM, Prabath Siriwardena
>> wrote:
>>
>>> Thanks Frank for the suggestion. Yes - it would be great if we can make
>>> the template gene
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 subjec
Sumedha,
does that mean that a client cannot use backward versions of an API? I.e.
that a client may break if it just uses http://localhost/app1 and gets a
new version of a response that it cannot process? I may have misunderstood
the mail-thread...
To avoid this, clients should be allowed to u
/services/oc-server/external/oc/clusters/{cluster-id}/commands/{command-id}
>> [7]
>> http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
>>
>> Thank you.
>>
>> Regards,
>> Chaya
>>
-id}
> [7]
> http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
>
> Thank you.
>
> Regards,
> Chaya
>
> Chaya Sandamali
> Software Engineering Intern
> WSo2 Inc
> Mobile: +94714905772
> LinkedI
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 wrote:
>
>> Hi Pulasthi,
>>
>> when you have "users without BPEL knowledge" in mind, you assume that
>> these users ha
provide a way to easily configure 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 L
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 :
> Hi,
>
> Following is the architecture of the workflow support framework. This was
> initially planned for IS, but can
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
d as you 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 wrote:
>
>> Hi Jo, hi Manu,
>>
>> how to cope
;>>
>>> Please let us know a convenient time for a call to discuss on it
>>> further.
>>>
>>> Also we will try to document these design decisions and concepts to
>>> benefit APIs created in the future.
>>>
>>> BTW. The changes were pushed to
nks
> Jo
>
>
> [1] http://hevayo.github.io/restful-apim/
>
> On Sat, Mar 28, 2015 at 12:47 AM, Frank Leymann wrote:
>
>> Hi Jo,
>>
>> again, thanks for your work: we'll get a nice RESTful API :-) In the
>> Richardson maturity model we'll get t
github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#securityDefinitionsObject
>
> [2] https://github.com/hevayo/restful-apim/blob/master/apim.yaml#L18-L19
>
> On Wed, Mar 25, 2015 at 3:51 PM, Frank Leymann wrote:
>
>> Hi Jo,
>>
>> nice piece of work!
>&g
]
>> http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
>>
>> Thank you.
>>
>> Regards,
>> Chaya
>>
>> Chaya Sandamali
>> Software Engineering Intern
>> WSo2 Inc
gt; [2] https://github.com/hevayo/restful-apim/blob/master/apim.yaml#L18-L19
>
> On Wed, Mar 25, 2015 at 3:51 PM, Frank Leymann wrote:
>
>> Hi Jo,
>>
>> nice piece of work!
>>
>> What is still needed is a description of the header fields for both, the
>>
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 :
> Hi All
>
> We are planing to implement a RESTFul API to expose the API Manager
> functionality. This will b
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 :
> Hi all,
>
> After the last review,we came up with a da
Hi,
I think the most important aspect is consistency across WSO2 products. All
WSO2 products should support the same set of representations of the
resources they manage. I.e., either all support both, XML as well as JSON,
or only JSON, or only XML. A product that deviates from this "rule" should
nodes (using colours
> or miniature overlay graphics) to achieve this?
>
> Put 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 L
2, Inc. - http://wso2.com/
>
>
> On Sun, Feb 22, 2015 at 6:00 PM, Frank Leymann wrote:
>
>> HI Jerad,
>>
>> thanks, the gif was helpful :-) Very nice tool!
>>
>> Coloring nodes is optional (I would even argue: not needed). But
>> coloring relations
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 r
eware.
>
> On Mon, Feb 16, 2015 at 1:21 PM, Gimantha Bandara
> wrote:
>
>> Hi Frank,
>>
>> Thanks you for your explanation!. What we currently do is, using *GET
>> /analytics/tables/{tableName} *get the whole table, if the table does
>> not exist, HTT
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 40
right,... (consistently) of the phase. And, yes, this means that we have
> to auto layout the diagram when theproximity
> annotations are requests, and we have to restore the diagram as modeled
> once display of annotations are switched off. Chevron diagrams are often
tionships. We can provide a button to turn
>> on/off arrows. When arrows are turned off, column ordering gives an
>> abstract visualization of chevron relationships. When arrows are turned on,
>> exact ordering can be viewed.
>>
>> Regards,
>> Chathura
>>
.e. if arrows are not drawn, all chevrons in a column are in successor
>> relationship with all chevrons in its previous column.
>>
>> Regards,
>> Chathura
>>
>> On Thu, Dec 11, 2014 at 11:50 PM, Frank Leymann wrote:
>>
>>> Hi Himasha,
>>>
n a column are in successor
> relationship with all chevrons in its previous column.
>
> Regards,
> Chathura
>
> On Thu, Dec 11, 2014 at 11:50 PM, Frank Leymann wrote:
>
>> Hi Himasha,
>>
>> very good idea :-)Let me suggest a little variation:
>>
>>
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
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 :
> Hi Srinath,
>
> Yes, if a process is already deployed, it can just store the deployment
> URL.
>
> An example scenario would be:
> An employee wants to claim
+1
Best regards,
Frank
2014-12-04 4:40 GMT+01:00 Chathura Ekanayake :
> 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 to execute a
> create_chevron page.
>
> 4.store_view:
>
>>
>>1. Again, I recommend to speak about Chevron Diagrams and not only
>>about "Chevron". Btw the same holds for "Process Model" instead of just
>>"Process"
>>
>>
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 alterna
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
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
https://mail.wso2.org/cgi-bin/mailman/listinfo
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 GMT+01:00
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 eac
urpose.
>
> Although 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" wrote:
>
>> This is true in general: even a simple statement l
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 :
> If yo
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 trigger
Hi Prabath, hi Fayaza,
I'll be in Colombo from 10/13 until 10/16. Maybe we find some time to
discuss the role of workflows in such kind of management activities on "key
resources"? This is a fundamental concept of TOSCA (that I contributed to)
which might be of interest to you...
Best regards,
1 - 100 of 102 matches
Mail list logo
