Hi All,
Adding architecture group.
Thanks and Regards,
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
Disclaimer: This communication may contain privileged or other confidential
information
Hi Asanka,
I had a look into the feature set and it looks really useful. Please send
us a PR and we will include this in a future ESB release.
On Wed, Mar 16, 2016 at 9:05 AM, Asanka Dissanayake
wrote:
> Hi All,
> I am developing a new Mediator for ESB as a pet project. After
Hi All,
I am developing a new Mediator for ESB as a pet project. After noticing
some draw backs in Payload Factory I thought of writing this one.
Code can be found at : https://github.com/asanka88/VelocityTemplateMediator
@ESB Team:
If this make any sense, I am more than happy to contribute this
Hi Rajjaz
,
We need to create a common module to improve re usability of the code.
But this common repo should not be just for
TOTP and HOTP
, but rather for the entire IS extensions. In this common repo
TOTP and HOTP
should be a component.
On Tue, Mar 15, 2016 at 10:34 PM, Rajjaz
If I understand the scope correctly, tooling should just be described as
part of the instructions for performing a particular task. I don't think it
will need its own section. Analytics, on the other hand, should be
described in topics like "Tracking usage" or other use cases that use
analytics.
Hi All,
Kind reminder on this topic.
@Prabath/Johan
shall we create a common module for TOTP and HOTP?
Algorithm based common module will reduce the codes and we can use for
multiple vendors, currently SMSOTP developed based on Nexmo API[1] but
there are multiple options available for send SMS.
Hi,
Yes. It is better if we can expose rendering information through rest api.
These data will be helpful when integrating bps runtime with process center
too.
Thanks,
Waruna
On Tue, Mar 15, 2016 at 5:30 PM, Vinod Kavinda wrote:
> Hi,
> Are we exposing these information via
Hi,
Are we exposing these information via REST api? It's better to expose
everything in REST first. Then we can build the UI as relevant, later.
Regards,
Vinod
On Mar 15, 2016 1:14 PM, "Nandika Jayawardana" wrote:
> Lets implement this for bpmn explorer as well. However, both
Our initial assumptions were wrong and we were able to narrow down this
issue to a wrong configuration parameter name. Due to that, we were always
running with a single disruptor event handler thread instead of a thread
pool. Now we are seeing better perf values with disruptor as opposed to the
Thanks for the update Jayanga.
On Tue, Mar 15, 2016 at 12:21 PM, Jayanga Kaushalya
wrote:
> Hi Himasha,
>
> We will be able to finish a JDBC based implementation for Platform with
> Authentication, Authorization, basic CRUD operations and claim management
> in around 3 weeks.
Lets implement this for bpmn explorer as well. However, both would change
when we move to C5.
Regards
Nandika
On Tue, Mar 15, 2016 at 12:31 PM, Vinod Kavinda wrote:
> [Adding Architecture@]
> Hi DiliniM,
> As we are planning on dropping the admin UIs with C5, is there a use of
[Adding Architecture@]
Hi DiliniM,
As we are planning on dropping the admin UIs with C5, is there a use of
integrating this with admin console UI? Shall we do this in our BPMN
explorer UI?
Regards,
Vinod
On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra wrote:
> Hi all,
>
> I
Hi Himasha,
We will be able to finish a JDBC based implementation for Platform with
Authentication, Authorization, basic CRUD operations and claim management
in around 3 weeks. We'll update you when we are done.
Thanks!
*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. |
Hi Amal,
Can you show the extension points we use inside the Apache CXF (Bus) box?
In addition to the invocation flow, can you also show how you handle the
service deployment?
Thanks,
KasunG
On Tue, Mar 15, 2016 at 11:03 AM, Amal Gunatilake wrote:
> Hi All,
>
> Following is
14 matches
Mail list logo