Hi Shazni, All of these three things are eventually moving out of kernel. MountHandler's dependency on RemoteRegistry needs to be removed. There is a special treatment for the RemoteRegistry in the mount handler, which is actually not required. We need to utilize proper OSGi practices for this.
Thanks, Senaka. On Wed, Jan 22, 2014 at 11:30 AM, Shazni Nazeer <[email protected]> wrote: > Hi Eranda, > > In the current context, MountHandler is dependant on the RemoteRegistry. I > think we need to retain MountHandler in the kernel. How will be the removal > of RemoteRegistry would affect that? > > regards, > > Shazni Nazeer > > Senior Software Engineer > > Mob : +94 715 440 607 > LinkedIn : http://lk.linkedin.com/in/shazninazeer > Blog : http://shazninazeer.blogspot.com > > > On Wed, Jan 22, 2014 at 11:09 AM, Shazni Nazeer <[email protected]> wrote: > >> >> Shazni Nazeer >> >> Senior Software Engineer >> >> Mob : +94 715 440 607 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> >> >> ---------- Forwarded message ---------- >> From: Kishanthan Thangarajah <[email protected]> >> Date: Wed, Jan 22, 2014 at 11:08 AM >> Subject: Re: [C5] Repository API/SPI >> To: Eranda Sooriyabandara <[email protected]> >> Cc: Shazni Nazeer <[email protected]>, WSO2 Engineering Group < >> [email protected]> >> >> >> Hi, >> >> Why are we discussing this privately? This should go to architecture@ >> >> >> On Wed, Jan 22, 2014 at 11:04 AM, Eranda Sooriyabandara >> <[email protected]>wrote: >> >>> Hi Shazni, >>> >>> >>> On Wed, Jan 22, 2014 at 10:56 AM, Shazni Nazeer <[email protected]> wrote: >>> >>>> Hi All, >>>> >>>> I'm starting this thread to discuss the Repository API/SPI design for >>>> the C5. >>>> >>>> I've been doing the refactoring of the existing registry kernel by >>>> introducing a new exception model across the code, refactoring the code to >>>> provide API methods, whereby earlier done with accessing implementation >>>> level classes like RegistryContext. Further I've been removing unwanted >>>> packages, classes and duplicate interfaces and methods in usable classes. >>>> >>>> These changes are also verified to be compatible with platform >>>> components by modifying the existing greg product to fit with the modified >>>> kernel and its integration test passes on mostly in par with the >>>> integration tests of the existing product. >>>> >>>> Now we need to clarify what exactly need to be in the Repository >>>> API/SPI. I've few questions to clarify on this? >>>> >>>> 1. Should we need to keep Comments, Tags, Aspects anymore in Repository >>>> API? >>>> >>> >>> IMO, we should be moving these to the platform level. >>> >>> >>>> >>>> 2. What's the decision on the UserRegistry (which keeps session >>>> information)? Should this remain in Repository code base? If so, is it in >>>> API? >>>> >>> >>> We may need to work on this once identity people finalize their APIs. >>> For now let's keep it as it is. >>> >>> >>>> >>>> 3. Is the RemoteRegistry going to be in the Repository? >>>> >>> >>> RemoteRegistry is a part of org.wso2.carbon.registry.app.* which not >>> exposing a java API, which should be move to platform. >>> >>> thanks >>> Eranda >>> >>> >>>> >>>> IMO, all these have to be removed. WDYT? >>>> >>>> regards, >>>> >>>> Shazni Nazeer >>>> >>>> Senior Software Engineer >>>> >>>> Mob : +94 715 440 607 >>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>> Blog : http://shazninazeer.blogspot.com >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "WSO2 Engineering Group" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit >>>> https://groups.google.com/a/wso2.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> >>> *Eranda Sooriyabandara*Senior Software Engineer; >>> Integration Technologies Team; >>> WSO2 Inc.; http://wso2.com >>> Lean . Enterprise . Middleware >>> >>> E-mail: eranda AT wso2.com >>> Mobile: +94 716 472 816 >>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >>> Blog: http://emsooriyabandara.blogspot.com/ >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "WSO2 Engineering Group" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit >>> https://groups.google.com/a/wso2.com/groups/opt_out. >>> >> >> >> >> -- >> *Kishanthan Thangarajah* >> Senior Software Engineer, >> Platform Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com >> <http://kishanthan.wordpress.com>* >> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
