I have a feeling its better to have Algorithm type and Algorithm in the
same level as Algorithm, and then have a tab inside to see all algos to
select one, and another tab to help selecting one algo
from recommendations.
Regards
Suho
On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi
Hi all,
Im working on Making the tenants subscription to stratos environments fault
tolerant [1]
This has been discussed in mail thread with subject - [Architecture] [AF]
Tenant subscribing to stratos environments - making it fault tolerant
*Issue*
**
There are some possible failure
In step 8/9, we ask the questions by default. The user has the option to
skip and go to the all algorithms view.
What happens after clicking on the build model? I am assuming it redirects
into home with current workflow expanded
Thanks.
On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva
Hi Harsha,
I see your point.
If you follow tenant creation bpel you may see initializeBuildManager
and initializeRepositoryManager
happens one after the other in a row. If it got failed in any step the
process won't continue.
But in last step of bpel you can see that initializeCloudManager is
Hi
On Wed, Dec 17, 2014 at 2:23 PM, Isuruwan Herath isuru...@wso2.com wrote:
[moved to architecture]
Hi Sameera,
Please see the comments inline.
On Mon, Dec 15, 2014 at 11:00 PM, Sameera Kannangara samee...@wso2.com
wrote:
Hi all,
$Subject refers to the functionality required to
You mean notification management component parse common configuration file
and pass relevant configurations to the notification sending modules at the
time of registering
Yes, Management component passes the relevant configurations and initialize
them.
or notification sending modules
Hi Mahesh,
+1 for the current design. I assume you have multiple instances of durable
subscribers for each subscription made to Stratos cartridges. For example,
if we have multiple tenant aware cartridges(App Server, UES Server, BPS
Server etc), the durable subscriber should be able to
Old UI had that sort of a workflow.. UX team suggested to avoid a wizard
inside a wizard for better user experience..
On Wed, Dec 17, 2014 at 12:49 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
I have a feeling its better to have Algorithm type and Algorithm in the
same level as
Suho's comment makes sense. Lets see what we can do about it without
affecting the workflow and consistency (without having to run two wizard
navigation).
Cheers
On Thu, Dec 18, 2014 at 8:47 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
Old UI had that sort of a workflow.. UX team
Hi Sameera,
On Wed, Dec 17, 2014 at 3:22 PM, Geeth Munasinghe ge...@wso2.com wrote:
Hi
On Wed, Dec 17, 2014 at 2:23 PM, Isuruwan Herath isuru...@wso2.com
wrote:
[moved to architecture]
Hi Sameera,
Please see the comments inline.
On Mon, Dec 15, 2014 at 11:00 PM, Sameera Kannangara
Hi All
I have updated the mockups based on the chat I had with Lochana in the
morning. Hope the page flow is much clear now.
*@Suho*, we have merged Algorithm Type and Algorithm in to the same level
based on your feedback (We adjusted it without using tabs.Having tabs in
this level makes things
Thanks for the feedback guys!
I will start working on the html stuff.
Cheers
On Thu, Dec 18, 2014 at 12:33 PM, Lochana Menikarachchi loch...@wso2.com
wrote:
Looks good..
On Thu, Dec 18, 2014 at 12:30 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
On Thu, Dec 18, 2014 at 12:04 PM,
12 matches
Mail list logo
