On Thu, Mar 6, 2014 at 11:49 AM, Senaka Fernando wrote:
> Hi Nuwan, Amila,
>
> If you for a moment think of a Store/Publisher webapp being a resource
> (just a logical assumption), is this kind of workflow similar to a registry
> lifecycle? We shouldn't be looking at the configuration model or wh
Hi Senaka,
If we assume a subscription being a resource, then the states it would go
through are somewhat similar to stages in a LifeCycle. When a subscription
is made a workflow will be triggered (the state will be set to Created) and
based on the configuration it will call an external service. T
Hi Nuwan, Amila,
If you for a moment think of a Store/Publisher webapp being a resource
(just a logical assumption), is this kind of workflow similar to a registry
lifecycle? We shouldn't be looking at the configuration model or what it
does today, but the functional similarity.
I'm asking these
>From what I understand, a registry lifecycle is always associated to a
registry resource (only). But workflows are plug-points to various UI
actions that you perform on the Store/Publisher webapps. Ex: A user
sign-up, API Subscription, etc.
Thanks,
NuwanD.
On Thu, Mar 6, 2014 at 11:28 AM, Senak
On Thu, Mar 6, 2014 at 11:04 AM, Amila De Silva wrote:
> Hi,
>
> Currently the configuration for Workflow Executors are kept in the
> api-manager.xml. Due to this design, there'll be a single workflow
> configuration for an entire deployment and all the tenants have to use the
> same executors.
>
Hi Amila,
How different are these workflow configurations from a registry lifecycle
configuration? I'm not suggesting that we reuse, but just to understand.
Thanks,
Senaka.
On Thu, Mar 6, 2014 at 11:04 AM, Amila De Silva wrote:
> Hi,
>
> Currently the configuration for Workflow Executors are
Hi,
Currently the configuration for Workflow Executors are kept in the
api-manager.xml. Due to this design, there'll be a single workflow
configuration for an entire deployment and all the tenants have to use the
same executors.
We are planning to move Workflow Configuration to the registry. A de
On Wed, Mar 5, 2014 at 3:10 PM, Sameera Jayasoma wrote:
> Hi Asela,
>
>
> On Wed, Mar 5, 2014 at 10:55 AM, Asela Pathberiya wrote:
>>
>> Hi All,
>>
>> In some Identity Server deployment, there are clients (web
>> applications, Application clients and so on) that talk to admin
>> services in Ident
Hi all
I found that our tenant creation process is calling reset password call
inside tenant creation process.
When we call tenant creation it goes through *persistTenant* call in
*TenantPersistor* class. And it calls *persistTenantInUserStore*. In the
end of this call it calls for *updateTenantAdm
Sameera, Thanks a lot for the great work within a short period of time.
/Ruchira
On Wed, Mar 5, 2014 at 5:38 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:
> Hello Everyone,
>
> The updated jaggery-pipe (pipe) and the router implementation is available
> at:
>
> https://github.com/s
Hi Sameera,
I have done some changes to the router. I'll contribute them back. This is
regarding the public api of the router.
Cheers~
On Wed, Mar 5, 2014 at 5:38 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:
> Hello Everyone,
>
> The updated jaggery-pipe (pipe) and the router impl
Hello Everyone,
The updated jaggery-pipe (pipe) and the router implementation is available
at:
https://github.com/splinter/jaggery-pipe
Thank You,
Sameera
On Mon, Feb 17, 2014 at 7:59 PM, Nuwan Bandara wrote:
> +1 for the proposal guys. and as chan said if we can use goose for base
> stuff l
Hi Asela,
On Wed, Mar 5, 2014 at 10:55 AM, Asela Pathberiya wrote:
> Hi All,
>
> In some Identity Server deployment, there are clients (web
> applications, Application clients and so on) that talk to admin
> services in Identity server such as user management, entitlement and
> s on... To acce
13 matches
Mail list logo
