Hi Sagara,

As Azeez mentioned there is an interface at CarbonUtils named as
CacheInvalidator. My component will implement this interface. We planned to
have the interface at CarbonUtils because every product will need this
service.

Thank you  & Best regards,

*Amal Gunatilake*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware


On Thu, Apr 17, 2014 at 6:03 AM, Afkham Azeez <az...@wso2.com> wrote:

>
>
>
> On Thu, Apr 17, 2014 at 12:33 AM, Sagara Gunathunga <sag...@wso2.com>wrote:
>
>>
>>
>>
>> On Wed, Apr 16, 2014 at 2:57 PM, Amal Gunatilake <am...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Following updates has been discussed on $subject.
>>>
>>> 1) Make the subscription auto subscribe once the jar bundle is present.
>>> 2) Check on how to resubscribe if the server goes down and comes up
>>> 3) If the sever goes down when a message receives check whether it
>>> queues the message and receive.
>>> 4) jndi.properties file
>>>
>>>    - If the file is already present at conf directory then load the
>>>    settings but if the expecting parameters not found put error log and show
>>>    the user needed parameters.
>>>    - If the file is not present then put the file to conf directory and
>>>    log a warning message
>>>
>>> 5) It was discussed whether we are going to use AMPQ instead JMS. This
>>> has to be determined which I will open a separate thread for discussion.
>>>
>>> 6) Generate UUID and do the message comparison to ignore own messages.
>>>
>>> 7) Let the topic name configurable.
>>>
>> Hi Amal,
>>
>> Have you define a clear API and separate it from JMS implementation ? IMO
>> having a clear API is must thing for this feature as we may have to include
>> some other implementations in future. I'm thinking about SNS based
>> implementation for future where EC2 users have freedom to use native
>> supported SNS based implementation effectively instead of bringing  and
>> configuring another message broker into the deployment setup.
>>
>
> There is an interface with a single method, and using JMS is just an
> implementation detail of Amal's component.
>
>>
>> Thanks !
>>
>>
>>> Please update the thread if there are any further updates.
>>>
>>>  Thank you  & Best regards,
>>>
>>> *Amal Gunatilake*
>>>  Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;    http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.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: **az...@wso2.com* <az...@wso2.com>
> * cell: +94 77 3320919 <%2B94%2077%203320919> 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
> <http://lk.linkedin.com/in/afkhamazeez>*
>
>
> *Lean . Enterprise . Middleware*
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to