On Sat, May 19, 2012 at 1:05 AM, Afkham Azeez <[email protected]> wrote:

> Ha ha... you have gone out of sync after leaving :P Check the dictionary.
>
> I guess I've missed the dash :) that is why I couldn't find this in any of
the dictionaries :P


> dep·sync   [dip-*sink*] 
> <http://dictionary.reference.com/help/luna/Spell_pron_key.html>
>  Show IPA
>  noun
> 1.
> Deployment Synchronizer.
> 2.
> The Carbon component that does deployment synchronization across a
> monolithic cluster.
>
> dep·sync   [dip-*sink*] 
> <http://dictionary.reference.com/help/luna/Spell_pron_key.html>
>  Show IPA
>  verb
> 1.
> Deployment Synchronization.
> 2.
> The act of synchronizing deployment artifacts across a monolithic cluster.
>
>
For me enabling Deployment synchronizer and enabling Axis2 clustering are
two independent operations. Deployment synchronizer does configuration
sync. Axis2 clustering does runtime information sharing among the cluster
nodes. 99% of the clustering scenarios doesn't require axis2 clustering and
only require configuration synchronization. So I think making axis2
clustering mandatory for enabling dep-sync :) is not a requirement.

Thanks,
Supun..


>  On Sat, May 19, 2012 at 10:14 AM, Supun Kamburugamuva 
> <[email protected]>wrote:
>
>> What is depsync?
>>
>> Thanks,
>> Supun..
>>
>> On Sat, May 19, 2012 at 12:33 AM, Afkham Azeez <[email protected]> wrote:
>>
>>>
>>>
>>> On Fri, May 18, 2012 at 11:22 PM, Kasun Gajasinghe <[email protected]>wrote:
>>>
>>>> Hi folks,
>>>>
>>>> Isn't the $subject the case now? Is there a way to overcome this?
>>>>
>>>> If $subject is the case, I think there should at least be a message in
>>>> the UI saying that the depsync doesn't work if Axis2 clustering is not
>>>> enabled via axis2.xml.
>>>>
>>>
>>> If depsync is enabled & clustering is not enabled, that component should
>>> throw an exception during startup, and if it is done through the UI, again
>>> it should provide an error message to the UI.
>>>
>>> Thanks,
>>>> --KasunG
>>>>
>>>> --
>>>> *Kasun Gajasinghe*
>>>> Software Engineer;
>>>> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
>>>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>>>> *
>>>>  *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>*
>>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>>>> *
>>>>
>>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * <http://www.apache.org/>**
>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Supun Kamburugamuva
>> Member, Apache Software Foundation; http://www.apache.org
>> E-mail: [email protected] <[email protected]>;  Mobile: +94 77 431 3585
>> Blog: http://supunk.blogspot.com
>>
>>
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: [email protected] <[email protected]>;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to