Yes, That is the kernel information. We need to have both kernel information and product information.
Regards Nandika On Thu, May 5, 2016 at 12:04 PM, Hasitha Aravinda <hasi...@wso2.com> wrote: > Carbon.yml contains following fields. I think we can use these for this > purpose. > > id: carbon-kernel #Value to uniquely identify a server > name: WSO2 Carbon Kernel #Server Name > version: 5.1.0-SNAPSHOT #Server Version > > Thanks, > Hasitha. > > On Thu, May 5, 2016 at 11:59 AM, Nandika Jayawardana <nand...@wso2.com> > wrote: > >> We have to be reading the product name and version number from the >> configuration file. Does the kernel provide a utility method to read the >> product info ?. For bps, we need to introduce a configuration file to BPS >> to keep product related information. >> >> Regards >> Nandika >> >> On Thu, May 5, 2016 at 11:02 AM, Himasha Guruge <himas...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> We have refactored our REST APIs by implementing Microservice interface. >>> According to the new REST guideline , we need to maintain the URL format >>> like below. For example, >>> >>> http://localhost:7777/bps/bpmn/v4.0/repository/deployments >>> >>> How are we going to maintain the product version updates with >>> microservices? If we are to maintain the product version with a parameter >>> been set from a config file, how can we achieve this? >>> >>> >>> Thanks, >>> Himasha Guruge >>> *Software Engineer* >>> WS*O2* *Inc.* >>> Mobile: +94 777459299 >>> himas...@wso2.com >>> >> >> >> >> -- >> Nandika Jayawardana >> WSO2 Inc ; http://wso2.com >> lean.enterprise.middleware >> > > > > -- > -- > Hasitha Aravinda, > Senior Software Engineer, > WSO2 Inc. > Email: hasi...@wso2.com > Mobile : +94 718 210 200 > -- Nandika Jayawardana WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
