Framework Specific Configuration on Documentation - V2

HTML5 - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

HTML5

Target Audience: CAST Administrators

Summary: This document provides a guide based on CAST’s field experience on how to configure Spring based applications using CAST AIP. These configurations are used over and above CAST AIP 8.2.x HTML5 offering (see Reference Materials below for links) to overcome limitations such as missing links. The applicability of this guide should have assessed for newer versions of CAST AIP and Extension.

Introduction to HTML5

This section gives a brief overview of the framework.

REST API - Java - DotNet - PHP - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

REST API Best Practice on Java, .Net & PHP
Contents

Target Audience: CAST Administrators

Summary: This documentation is aimed at CAST Administrators who would need to configure REST based applications using CAST AIP. It provides a guide based on field experience of how best to configure REST based applications using CAST AIP so that similar configurations can be reused. The typical examples given below have been applied on different versions of CAST AIP based on various requirements.

ASP.NET MVC - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

Target Audience: CAST Administrators

Summary: This document provides a guide based on CAST’s field experience on how to configure Spring based applications using CAST AIP. These configurations are used over and above CAST AIP 8.2.x ASP.NET MVC offering (see Reference Materials below for links) to overcome limitations such as missing links. The applicability of this guide should have assessed for newer versions of CAST AIP and Extension.

Introduction to ASP.NET MVC

This section gives a brief overview of the framework.
The Model-View-Controller (MVC) architectural pattern separates an application into three main components: the model, the view, and the controller. The ASP.NET MVC framework provides an alternative to the ASP.NET Web Forms pattern for creating Web applications. The ASP.NET MVC framework is a lightweight, highly testable presentation framework that (as with Web Forms-based applications) is integrated with existing ASP.NET features, such as master pages and membership-based authentication. The MVC framework is defined in the System.Web.Mvc assembly.

SWING and AWT - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

Target Audience: CAST Administrators

Summary: This document provides a guide based on CAST’s field experience on how to configure Swing and AWT based applications using CAST AIP. These configurations are used all versions of CAST AIP 8.2.x and above for Swing and AWT offering (see Reference Materials below for links) to overcome limitations such as missing links. The applicability of this guide should have assessed for newer versions of CAST AIP and Extension.

Java GWT - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

Target Audience: CAST Administrators

Summary: This document provides a guide based on CAST’s field experience on how to configure GWT based applications using CAST AIP. These configurations are used all versions of CAST AIP 8.2.x and above for GWT offering (see Reference Materials below for links) to overcome limitations such as missing links. The applicability of this guide should have assessed for newer versions of CAST AIP and Extension.

Introduction to GWT

This section gives a brief overview of the framework.

AngularJS - Best Practice

Mon, 01 Jan 0001 00:00:00 +0000

Target Audience: CAST Administrators

Summary: This document provides a guide based on CAST’s field experience on how to configure AngularJS based applications using CAST AIP. These configurations are used all versions of CAST AIP 8.2.x and above for AngularJS offering (see Reference Materials below for links) to overcome limitations such as missing links. The applicability of this guide should have assessed for newer versions of CAST AIP and Extension.

Introduction to AngularJS

This section gives a brief overview of the framework.

AETP - AEFP Documentation for - for Java and DotNet

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

We have identified the ideal ratio of AETP vs AEFP on the basis of the historical analysis of applications on-boarded. We have identified various Technology stacks ( for e.g. N-tier, client-server etc). Candidate Applications will be tagged into identified Technology stacks. An application will be either in one or other stack, if an application is falling under multiple stacks then it will be tagged into the best matching stack on the basis of code % of particular technology ( for E.g. if an N-tier application has mobile technology source code then manually on the basis of code coverage it will be identified if this application will be tagged into N-tier or Mobile Stack.)