Hi all, In our platform there are several types of configuration mechanisms used.
1. Files in repository/conf 2. Registry / database 3. Deployable artifacts In deployable artifacts WSO2 have unique archive type, Carbon artifacts. But this carbon story is fully supported by only several products. ESB artifacts like sequences and proxy services act as first class members. Jaggery also have the first class citizenship in Carbon artifacts. Well known artifacts types like WAR files and AAR files too are also supported. But BAM has its own archive type TBOX for its samples. CEP is also moving to the TBOX archive type. And toolboxes too contain same artifacts like Jaggery while Jaggery already has the full citizenship in CAR files. And toolboxes use its own deployment strategy while Carbon artifacts have it own. Why cannot all the WSO2 products go for the same Carbon artifact type? If all stream definitions, event input adaptors and etc. can be given the first class Carbon citizenship, we can simplify our deployment strategy. Instead of toolboxes we can use CAR files. In a too much toolbox scenario we can use a tool like Dev-Studio to merge CAR files. (I don't know whether this feature is already available) And for products like WSO2 IS, if we can define artifact types such as Service Providers and Identity Providers and provide them the first class citizenship (like the existing sequences and proxy services) as well, won't it simplify the deployment of a complex system and simplify the artifact deployment strategy? WDYT? Thanks. *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : [email protected] *Skype* : @manindae *Twitter* : @maninda
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
