Re: Meta Data Service Client as a Separate Component

Hi Lahiru, We faced some issues with RestEasy library and JAX-RS based libraries. We couldn't get them to work within the Carbon platform because of some ClassDef not found issue. So I guess we will have to stick with Apache HTTP library and write a wrapper. On Mon, Sep 22, 2014 at 5:32 PM, Lahir

Re: Meta Data Service Client as a Separate Component

+1 for a generic client as code would be easy to manage if so. Nirmal has suggested "RestEasy" at the thread "Java client for Kubernetes REST API". It seems that is a good library. Shall we stick to that? Thanks. On Fri, Sep 19, 2014 at 1:12 PM, Sajith Kariyawasam wrote: > > On Thu, Sep 18, 20

Re: Meta Data Service Client as a Separate Component

On Thu, Sep 18, 2014 at 5:21 PM, Isuru Haththotuwa wrote: > Hi Akila, > > I'm not aware if there is a generic carbon component for this. But, I > totally agree with the second point; we can implement a generic rest > client. Currently we have one in the CLI, and now we are going to have the > sam

Re: Meta Data Service Client as a Separate Component

This is the initial API that I came with for the meta data service client component. /** * Initialize the MetaDataServiceClient. Should be called once before using the MetaDataServiceClient. * @throws MetaDataServiceClientExeption */ public void initialize () throws MetaData

Re: Meta Data Service Client as a Separate Component

Hi Akila, I'm not aware if there is a generic carbon component for this. But, I totally agree with the second point; we can implement a generic rest client. Currently we have one in the CLI, and now we are going to have the same for Kubernetes and Meta Data service clients. We can put all the requ

Re: Meta Data Service Client as a Separate Component

Hi Isuru, Thanks for the explanation. Don't we have a Carbon platform component to achieve this? Just making sure we are not replicating the functionality. Can we create a generic REST client that can be used for communicating with other REST services too? For eg - we need to have a REST client

Re: Meta Data Service Client as a Separate Component

Hi Akila, On Thu, Sep 18, 2014 at 2:09 PM, Akila Ravihansa Perera wrote: > +1 > > Meta-data service is going to be vital when implementing clustering > support for application services as well. I think it's better to have > it as a separate component. > > Could you please explain what component

Re: Meta Data Service Client as a Separate Component

+1 Meta-data service is going to be vital when implementing clustering support for application services as well. I think it's better to have it as a separate component. Could you please explain what components will have dependencies to the meta-data service client? This is going to be a REST cli

Meta Data Service Client as a Separate Component

Hi Devs, In Service Grouping, we would heavily need to use the meta data service to put and get data. Therefore, shall we implement a $subject? Then it can be re-used wherever required across Stratos. WDYT? -- Thanks and Regards, Isuru H. +94 716 358 048* *