Hello all,
As a requirement of WSO2 Corporate Asset Store [1] which is an extension of
Enterprise Store, we need to have a system to send email notifications to
relevant people when a state of the life cycle of a certain asset is
changed. From asset type to asset type, the receivers can be
Hi
Please see my in line comment.
-- Forwarded message --
From: Selvaratnam Uthaiyashankar shan...@wso2.com
Date: Wed, Mar 19, 2014 at 8:35 AM
Subject: Re: [Architecture] Summary report of the meeting of the C5 Jaggery
based UI Framework - Architecture discussion which wa
In a
This is an important requirement (and it's in our pipeline as well). I
believe - we can incorporate these changes to the jaggery-executor (in
lifecycle state change). One thing we'll have to decide is the subscription
model used for users to the notifications.
Cheers~
On Wed, Mar 19, 2014 at
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
tenant-axis2.xml is used when populating the tenant axisConfiguration (each
tenant gets its own tenantAxisConfig during execution). These changes
should be added to that as-well to get this to work in tenant mode.
On Wed, Mar 19, 2014 at 12:23 PM, Manoj Kumara ma...@wso2.com wrote:
Hi Sameera,
Hi Dushan,
OAuth 2.0 flow includes the redirection to the OAuth Dialog Page[1]. Is
there any workround to handle this within the ESB?
[1] https://developer.surveymonkey.com/mashery/guide_oauth
Thanks
BR
Indika Kularathne
On Wed, Mar 19, 2014 at 7:53 AM, Dushan Abeyruwan dus...@wso2.com
Hi all,
Sorry, lost this thread somehow, :).
Hi Samisa,
With regards to governed workflow, I don't think its mandatory for ES,
because most of the artefacts you'd find in ES, will simply have state.
But, of course there can be some that need a governed workflow. For this
we can either extend ES
