+1

On Sunday, February 13, 2011, Tharindu Mathew <thari...@wso2.com> wrote:
>
>
> On Sun, Feb 13, 2011 at 9:50 AM, Amila Suriarachchi <am...@wso2.com> wrote:
>
>
>
> On Sun, Feb 13, 2011 at 8:48 AM, Afkham Azeez <az...@wso2.com> wrote:
>
>
> This is something urgently needed for mars since the existing synchronizer 
> has many issues. So Mars cannnot live with it. Can we get this fixed urgently?
> Registry still uses the old event implementation. so we need to figure out 
> which version should have this feature.
>
> In the new model if the Qpid support this we can add the feature easily.
>
> To avoid this issue of old and new event implementation, shall we have a 
> hackathon to move all products to the new implementation?
>
> thanks,
> Amila.
>
>
>
> ------
> Sent from my APD®
> On Feb 13, 2011 12:09 AM, "Hiranya Jayathilaka" <hira...@wso2.com> wrote:> Hi,
>>
>> On Sat, Feb 12, 2011 at 9:29 PM, Amila Suriarachchi <am...@wso2.com> wrote:
>>
>>>
>>>
>>> On Sat, Feb 12, 2011 at 9:15 PM, Senaka Fernando <sen...@wso2.com> wrote:
>>>
>>>> Hi Hiranya,
>>>>
>>>> On Sat, Feb 12, 2011 at 3:17 PM, Hiranya Jayathilaka 
>>>> <hira...@wso2.com>wrote:
>>>>
>>>>> Hi Folks,
>>>>>
>>>>> I have developed a component which subscribes for the CollectionUpdate
>>>>> event of a particular collection in the registry
>>>>> (/repository/deployment/server). This collection can have a lot of
>>>>> sub-collections and child resources. Now if I add/remove a resource 
>>>>> directly
>>>>> under the above collection my component receives the update event. But if
>>>>> something happens in a sub-collection or if I update a child resource (eg:
>>>>> modify content) nothing happens.
>>>>>
>>>>> Is there a way to subscribe to the collection, so that any update to the
>>>>> collection or its children will fire an event?
>>>>>
>>>>
>>>> IIRC, Srinath, and I discussed this before, and we agreed to provide some
>>>> mechanism to programatically subscribe to /foo/bar/* which will make it
>>>> possible to capture events for sub-collections under bar. I'm not sure
>>>> whether this made it to the event component's source code.
>>>>
>>>
>>> This feature is not there with the existing code. (both new and old) But we
>>> plan to put it in a future release.
>>>
>>
>> Thanks Amila and Senaka for the clarifications. Based on this it seems we
>> have to change our plans for the deployment synchronizer component (registry
>> based repository) a little bit. Our intention was to use the registry
>> eventing model to monitor the collection and checkout the contents to the
>> file system only when needed. We'll have to live with the existing periodic
>> checkout model for a while until this feature is implemented in registry
>> eventing.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> thanks,
>>> Amila.
>>>
>>>>
>>>> From the Registry PoV we generate events for all updates, and we rely on
>>>> the SubscriptionManager to return a list of endpoints subscribed to a 
>>>> topic.
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>>>
>>>>> Thanks
>>>>> --
>>>>> Hiranya Jayathilaka
>>>>> Senior Software Engineer;
>>>>> WSO2 Inc.;  http://wso2.org
>>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>
>>>>> _______________________________________________
>>>>> Carbon-dev mailing list
>>>>> Carbon-dev@wso2.org
>>>>> 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
>
> --
> Regards,
>
> Tharindu Mathew
> Software Engineer,WSO2 Inc.,http://wso2.com
>
>

-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*
email: **az...@wso2.com* <az...@wso2.com>* 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
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to