+1 for reducing the number of templates and complexities in generating the synapse configs out of those. Current model does not scale very well.
@Joe, can you share a simple sample of what you are intending to do? With the current approach, users can easily edit the template and change the synapse configs of the APIs. We will not be losing this facility by introducing velocity right? Thanks, NuwanD. On Mon, Oct 28, 2013 at 10:08 PM, Joseph Fonseka <[email protected]> wrote: > > Hi All > > Shall we use Apache Velocity to generate synapse config for APIs. Key > benefits using Velocity over current method are. > > 1. Will be able to reduce the existing number of template files. ( Eg. To > enable / disable JWT only need to use If condition inside the template ) > > 2. Can move most of the config generating logic in to the template thus > reducing the complexity of the template builders. > > 3. Can come up with more powerful and flexible templates. ( Eg. If tenant > id is passed to template user can customize how the apis are generated > based on tenants ) > > Apache Velocity is already included in APIM so we do not need additional > dependencies. > > Regards > Jo > > -- > *Joseph Fonseka* > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 772 512 430 > skype: jpfonseka > > * <http://lk.linkedin.com/in/rumeshbandara>* > > -- Nuwan Dias Senior Software Engineer - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
