Hi all, It seems we are continuing with Toolbox as the default archive type instead of going with Carbon archives. I have started a architecture mail thread titled "WSO2 Configuration deployment dilemma" discussing this conflict.
As Isabelle says there will be variety of requirements of adding new artifact types in future. Instead of going with hierarchical directory structures like "input/adaptors" and "uis/gadgets" I think it is better to go for a generic way of locating artifacts in an archive file with a distinguished name like "org.wso2.carbon.input.adaptors", "org.wso2.carbon.ues.gadgets" and "org.wso2.carbon.esb.sequences" (as "Synapse" will no long be used) in a flat directory structure. (like we keep all different OSGi bundles in the same plugins directory) This will enable us to add third party artifacts also in future without restructuring the existing artifact locations. With this standard we can maintain all the artifact types required by the Carbon platform in a single .car file. *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : [email protected] *Skype* : @manindae *Twitter* : @maninda On Thu, Oct 30, 2014 at 9:46 PM, Isabelle Mauny <[email protected]> wrote: > Hi Mohan, > > A detail but I would avoid using product names such as Jasper or Hive - > This may evolve over time (even if not short term) and we would need to > change the toolbox install process if underlying technology was changed. > > Isabelle. > > ------------------------------------------------------------------------------------- > *Isabelle Mauny* > VP, Product Management; WSO2, Inc.; http://wso2.com/ > > On Thu, Oct 30, 2014 at 9:09 AM, Mohanadarshan Vivekanandalingam < > [email protected]> wrote: > >> >> >> On Thu, Oct 30, 2014 at 8:30 PM, Sriskandarajah Suhothayan <[email protected] >> > wrote: >> >>> Hi >>> >>> The current folder structure[1] does not extend clearly for CEP >>> integration and hence we have to decide on the new folder structure of the >>> Analytics Toolbox. shall we have >>> >>> inputs >>> - adaptors >>> - builders >>> outputs >>> - adaptors >>> - formatters >>> streams >>> uis >>> - gadgets >>> - jaggery-apps >>> reports >>> - jesper >>> analytics >>> - executionplans >>> - hive-scrips >>> >>> Thoughts? >>> >> >> +1.. Above structure covers all the artifacts which are available at the >> moment. I think analyzers.properties file is missed in above, what is the >> best place for that (anaytics or new folder called scheduler) ?? >> >> Thanks, >> Mohan >> >>> >>> Regards >>> Suho >>> >>> [1]https://docs.wso2.com/display/BAM200/Creating+a+Custom+Toolbox >>> >>> -- >>> >>> *S. Suhothayan* >>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>> *WSO2 Inc. *http://wso2.com >>> * <http://wso2.com/>* >>> lean . enterprise . middleware >>> >>> >>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >>> >> >> >> >> -- >> *V. Mohanadarshan* >> *Software Engineer,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com <http://wso2.com> * >> *lean.enterprise.middleware.* >> >> email: [email protected] >> phone:(+94) 771117673 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
