Hi all,
I've been working on the $subject and currently there's only one task
remaining to be completed. The main intention of this effort is to migrate
the existing task implementation of BAM to ntasks which is a quartz based
task scheduler component introduced a couple of months back. While
On Mon, Mar 26, 2012 at 12:04 PM, Prabath Abeysekera praba...@wso2.comwrote:
Hi all,
I've been working on the $subject and currently there's only one task
remaining to be completed. The main intention of this effort is to migrate
the existing task implementation of BAM to ntasks which is a
The reason that ntask expects string key value pairs is to be able to
execute tasks in a distributed manner. As part of completing the task, you
should setup a few nodes and check whether tasks are distributed
appropriately and in a fail over manner.
Also, try to expose some MXBeans to check how
On Mon, Mar 26, 2012 at 12:45 PM, Tharindu Mathew thari...@wso2.com wrote:
The reason that ntask expects string key value pairs is to be able to
execute tasks in a distributed manner. As part of completing the task, you
should setup a few nodes and check whether tasks are distributed
Hi Prabath,
Great, and by the way, the ntask component is working perfectly fine, and
it has been integrated into G-Reg. I'm just wondering whether these changes
would in anyway impact the existing component?
Thanks,
Senaka.
On Mon, Mar 26, 2012 at 1:19 PM, Prabath Abeysekera
