On Wed, May 18, 2011 at 10:14 AM, Hiranya Jayathilaka <[email protected]>wrote:

>
>
> On Wed, May 18, 2011 at 12:45 AM, Senaka Fernando <[email protected]> wrote:
>
>>
>>
>> On Wed, May 18, 2011 at 12:30 AM, Afkham Azeez <[email protected]> wrote:
>>
>>>
>>>
>>> On Wed, May 18, 2011 at 12:26 AM, Isuru Suriarachchi <[email protected]>wrote:
>>>
>>>> Hi all,
>>>>
>>>> Currently Deployment Synchronizer is not shipped with AS, DSS etc. by
>>>> default. But I think this is a very important feature for all products 
>>>> which
>>>> are using the Axis2 repository and clustered most of the time in production
>>>> environments. Therefore, I think this should be shipped with AS, ESB, DSS
>>>> and BRS. WDYT??
>>>>
>>>
> +1 We already ship it with ESB
>
>
>>
>>>> We already have an issue for this at [1]. However, Registry Community
>>>> Features are needed for Deployment Synchronizer. Hiranya, can you please
>>>> explain why and can't it work without that at all?
>>>>
>>>
>>> Please split the community features, if required. I guess some util
>>> methods/classes are used from it.
>>>
>>
>> +1. Hiranya, is it required to be able to add/remove subscriptions from
>> the Registry Browser UI? If not, we can move the registry eventing BE stuff
>> into another feature, so that the deployment synchronizer can use that.
>>
>
> It's only using registry eventing (org.wso2.carbon.registry.eventing). And
> even that's optional. User can specify when enabling the synchronizer
> whether to use eventing or use simple periodic synchronization. Is there a
> separate feature through which we can get the above component?
>

You can simply import the registry eventing bundle from the registry
community feature instead of importing the  whole features.

Sameera.

>
> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> Senaka.
>>
>>
>>>> Thanks,
>>>> ~Isuru
>>>>
>>>> [1] https://wso2.org/jira/browse/CARBON-10010
>>>>
>>>> --
>>>> Isuru Suriarachchi
>>>> Technical Lead & Product Manager, WSO2 Application Server
>>>> WSO2 Inc. http://wso2.com
>>>> email : [email protected]
>>>> blog : http://isurues.wordpress.com/
>>>>
>>>> lean . enterprise . middleware
>>>>
>>>>
>>>> _______________________________________________
>>>> Carbon-dev mailing list
>>>> [email protected]
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *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*
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: [email protected];  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: [email protected]
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to