Sorry I couldn't reply to this earlier. We have an abstraction for this purpose, and these four categories (Application, Data, Framework and LB) are the currently identified concrete implementations. So, the code is pretty much generic there, and we don't have to use long if-else ladders in the program flow. As Damitha mentioned in his reply as well, if there is a complete new cartridge category in the future, there will be code changes, but having this abstraction will help to integrate the new category easily.
On Thu, Jan 23, 2014 at 1:09 PM, damitha kumarage <[email protected]>wrote: > Hi, > > >> Defining catridges/types & plugging them in should solely be at the >>> discretion of the users who deploy the PaaS framework. >>> >> > Existing cartridge types are defined encapsulating the knowledge we > currently have on cartridge functionalities. If requirement arise for new > cartridge types then AFAIK it is not possible to add that functionality to > Stratos code without patching here and there(correct me if I'am wrong). In > order to allow smooth integration of such types I guess we need to abstract > out cartridge type functionalities in the code with proper design so that > new types can be plugged in. > > Damitha > > > > -- > __________________________________________________________________ > Damitha Kumarage > http://people.apache.org/ > __________________________________________________________________ > -- Thanks and Regards, Isuru H. +94 716 358 048* <http://wso2.com/>*
