Shall we put CacheInvalidator into the javax.cache.wso2 Maven module, under an org.wso2.carbon.caching package?
On Fri, Apr 25, 2014 at 2:08 PM, Shazni Nazeer <[email protected]> wrote: > Hi Amal, > > I can't build the kernel due to a cyclic dependency between > javax.cache.wso2 and the org.wso2.carbon.util. IMO CacheInvalidator > interface needs to be moved to some other package. > > Shazni Nazeer > > Senior Software Engineer > > Mob : +94 715 440 607 > LinkedIn : http://lk.linkedin.com/in/shazninazeer > Blog : http://shazninazeer.blogspot.com > > > On Thu, Apr 24, 2014 at 12:17 PM, Amal Gunatilake <[email protected]> wrote: > >> Hi Shezni, >> >> I have committed the code in my kernel git fork : >> https://github.com/amalhub/carbon4-kernel >> Please proceed and let me know if you have any queries. >> >> Thank you. >> >> Thank you & Best regards, >> >> *Amal Gunatilake* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> >> On Thu, Apr 24, 2014 at 10:58 AM, Shazni Nazeer <[email protected]> wrote: >> >>> Hi Subash, >>> >>> Yes I can proceed now onwards. >>> >>> @Amal - Can you provide me the git url where this is committed, so that >>> I can get a fork and perform the work. >>> >>> regards >>> >>> Shazni Nazeer >>> >>> Senior Software Engineer >>> >>> Mob : +94 715 440 607 >>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>> Blog : http://shazninazeer.blogspot.com >>> >>> >>> On Thu, Apr 24, 2014 at 10:52 AM, Subash Chaturanga <[email protected]>wrote: >>> >>>> Hi Amal, >>>> You've done a great job on initiating this and implementing to this >>>> point. Shazni is assigned from G-Reg to work on this with you and refactor >>>> this from our side. But since you locally test this and seems fine I hope >>>> Shazni can now get your PULL request and try to verify it in Kernel with >>>> the build and then proceed on refactoring registry accordingly. >>>> >>>> Hi Shazni, >>>> As discussed offline before, since we are running out of time, could >>>> you please proceed from this point now. I hope Amal will be able to help >>>> you if we have any issues(steps to setup and etc). >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> On Thu, Apr 24, 2014 at 10:42 AM, Amal Gunatilake <[email protected]>wrote: >>>> >>>>> Hi Subash, >>>>> >>>>> As per the offline discussion we had, I have moved the MB properties >>>>> to cache.xml and the component is finalized now >>>>> [1]<https://svn.wso2.org/repos/wso2/scratch/amalg/cache-invalidation-v3/>. >>>>> I have moved the code into kernel in my local machine and seems fine, but >>>>> before I commit, I have to make sure nothing breaks the kernel build. >>>>> Since >>>>> I'm in support I'm creating an urgent patch for a support issue and I will >>>>> be able to finish it by today. Then I will commit the code to git after >>>>> testing the component properly. >>>>> >>>>> [1] >>>>> https://svn.wso2.org/repos/wso2/scratch/amalg/cache-invalidation-v3/ >>>>> >>>>> Thank you & Best regards, >>>>> >>>>> *Amal Gunatilake* >>>>> Software Engineer >>>>> WSO2 Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> >>>>> On Tue, Apr 22, 2014 at 11:31 AM, Subash Chaturanga >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi Amal, >>>>>> Please move the code to the aforesaid place and Shazni will be >>>>>> working with you on moving registry related caching invalidation to new >>>>>> impl. Please help him to configure on how to, and also we need to >>>>>> document >>>>>> this. >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> On Tue, Apr 22, 2014 at 11:22 AM, Afkham Azeez <[email protected]>wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Apr 22, 2014 at 10:48 AM, Subash Chaturanga <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi Amal, >>>>>>>> Yes we have to push this to carbon kernel git repo and AFAIR we >>>>>>>> decided to make this a generic module that can be reused by the >>>>>>>> platform. >>>>>>>> I believe the package name is also >>>>>>>> finalized(org.wso2.carbon.caching.invalidator) ? >>>>>>>> >>>>>>>> I think it is better if we can move this in to carbon4-kernel / >>>>>>>> core / org.wso2.carbon.caching.core and put this under a new package >>>>>>>> named >>>>>>>> "invalidator" and the package name will be >>>>>>>> "org.wso2.carbon.caching.core.invalidator" . Azeez WDYT ? >>>>>>>> >>>>>>> >>>>>>> I am fine with that as long as the subscription to the topic does >>>>>>> not automatically happen if that code is there. In most cases, we will >>>>>>> not >>>>>>> need this global cache invalidation, so that code should not get >>>>>>> executed. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Apr 21, 2014 at 2:13 PM, Amal Gunatilake <[email protected]>wrote: >>>>>>>> >>>>>>>>> Hi Subash, >>>>>>>>> >>>>>>>>> Sorry for the delay. Since I'm in support I didn't have much time >>>>>>>>> to accelerate the process and during the weekend I managed to finish >>>>>>>>> all >>>>>>>>> the TODOs. Currently it's not yet in kernal git repo. I have the >>>>>>>>> latest >>>>>>>>> code in >>>>>>>>> https://svn.wso2.org/repos/wso2/scratch/amalg/cache-invalidation-v2/. >>>>>>>>> Please let me know into which path I should commit the code and I can >>>>>>>>> add >>>>>>>>> it to git repo immediately. >>>>>>>>> >>>>>>>>> Thank you & Best regards, >>>>>>>>> >>>>>>>>> *Amal Gunatilake* >>>>>>>>> Software Engineer >>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Apr 17, 2014 at 9:25 PM, Subash Chaturanga < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hi Amal, >>>>>>>>>> Let us know once the TODOs done in the code review except the JMS >>>>>>>>>> alternative discussion. One of G-Reg R&D folk will assign on >>>>>>>>>> migrating >>>>>>>>>> GReg cache invalidation to this pub sub impl. I hope now your >>>>>>>>>> component is >>>>>>>>>> in the kernel git repo. >>>>>>>>>> >>>>>>>>>> Hi Azeez,Sagara >>>>>>>>>> Once registry and user permission moved to this impl, it needs >>>>>>>>>> quite amount of testing on production aspects. Since this is almost >>>>>>>>>> a new >>>>>>>>>> feature and this leads documentation change in all products >>>>>>>>>> (mounting/caching) I believe we should not provide this as a patch >>>>>>>>>> for a >>>>>>>>>> customer unless it is really required. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Apr 17, 2014 at 10:37 AM, Amal Gunatilake <[email protected] >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> 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 <[email protected]>wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Apr 17, 2014 at 12:33 AM, Sagara Gunathunga < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Apr 16, 2014 at 2:57 PM, Amal Gunatilake < >>>>>>>>>>>>> [email protected]> 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 >>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>> 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: **[email protected]* <[email protected]> >>>>>>>>>>>> * 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 >>>>>>>>>>> [email protected] >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Thanks >>>>>>>>>> /subash >>>>>>>>>> >>>>>>>>>> *Subash Chaturanga* >>>>>>>>>> Senior Software Engineer :Integration TG; WSO2 Inc. >>>>>>>>>> http://wso2.com >>>>>>>>>> >>>>>>>>>> email: [email protected] >>>>>>>>>> blog: http://subashsdm.blogspot.com/ >>>>>>>>>> twitter: @subash89 >>>>>>>>>> phone: +9477 2225922 >>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks >>>>>>>> /subash >>>>>>>> >>>>>>>> *Subash Chaturanga* >>>>>>>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com >>>>>>>> >>>>>>>> email: [email protected] >>>>>>>> blog: http://subashsdm.blogspot.com/ >>>>>>>> twitter: @subash89 >>>>>>>> phone: +9477 2225922 >>>>>>>> Lean . Enterprise . Middleware >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *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 <%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* >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks >>>>>> /subash >>>>>> >>>>>> *Subash Chaturanga* >>>>>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com >>>>>> >>>>>> email: [email protected] >>>>>> blog: http://subashsdm.blogspot.com/ >>>>>> twitter: @subash89 >>>>>> phone: +9477 2225922 >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks >>>> /subash >>>> >>>> *Subash Chaturanga* >>>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com >>>> >>>> email: [email protected] >>>> blog: http://subashsdm.blogspot.com/ >>>> twitter: @subash89 >>>> phone: +9477 2225922 >>>> Lean . Enterprise . Middleware >>>> >>> >>> >> > -- *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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
