| OnTra™ Technology Framework Advantages |
|
| The OnTra™ Technology Framework ( OnTra™ Technology Framework ) is based on Java based n tier architecture. The architecture and design allow Client to achieve. |
|
| |
 |
Horizontal Scalability on all layers (Presentation, Application & Data store) |
| |
|
Open Standard Conformity (Easier support, Maintainability & Migration capability) |
| |
|
Cost Effective technology (Upfront and Ongoing costs) |
| |
|
Easier development, Maintenance and extendibility of modules |
|
| Some of the other advantages of using OnTra™ Technology Framework in travel based solutions are as follows |
|
| |
|
Based on the latest and emerging technologies |
| |
|
Open standards (J2EE) MVC Based Multi tier architecture |
| |
|
Vendor / Platform independent (Complete freedom of choice on Web, Application and Database Layers) |
| |
|
Extensible through SOAP/XML. OTA Compliance |
| |
|
Distributed Architecture and Application level clustering |
| |
|
Web based system with ability to have multiple participants four layers of security architecture |
| |
|
Modular: The framework allows for addition of modules on the same platform without any implications on the other module. |
| |
|
|
| JSF Framework – Core Framework of OnTra™ Technology Framework (Introduction) |
|
| The OnTra™ Technology Framework is based on the cutting edge JSF framework. This framework fors the technology ground for building user interfaces on the OnTra™ Technology Framework . The Java Server Faces technology includes: |
|
| |
|
A set of APIs for: representing UI components and managing their state, handling events and input validation, defining page navigation, and supporting internationalization and accessibility. |
|
| |
|
A JavaServer Pages (JSP) custom tag library for expressing a JavaServer Faces interface within a JSP page. |
|
| With the simple, well-defined programming model that JavaServer Faces technology provides, developers of varying skill levels can quickly and easily build Web applications by: assembling reusable UI components in a page, connecting these components to an application data source, and wiring client-generated events to server-side event handlers. With the power of JavaServer Faces technology, these web applications handle all of the complexity of managing the user interface on the server, allows the application developer to focus on their application code. |
| |
| Benefits of Using JSF |
|
The primary benefits of JavaServer Faces technology include: |
|
| |
|
Ease-of-Use: Several aspects of the JavaServer Faces architecture contribute to its ease-of-use. For one, JavaServer Faces technology is a clean separation between logic and presentation, enabling a wide range of users -- from web-page designers to component developers-- to take advantage of JavaServer technology, resulting in a division of labor and a shorter development cycle. Also, a user-interface created with JavaServer Faces technology handles all the complexities of user-interface management, including input validation, component-state management, page navigation, and event handling. |
|
| |
|
Standardization: JavaServer Faces technology is developed through the Java Community Process, under JSR-127. Several prominent, respected tools vendors are contributing members of the JSR-127 expert group and are committed to supporting JavaServer Faces technology in their tools. |
|
| |
|
Device Independence: JavaServer Faces technology is designed to be flexible. By defining only component functionality in extensible UI component classes, the JavaServer Faces architecture allows component developers to extend the component classes to generate their own component tag libraries targeted for specific clients. |
|
| |
|
New age technologies /Mobile interfacing: JSF technology enables the interfaces to be deployed over mobile devices other emerging channels with very few changes. Considerable support is available for upcoming technologies as comparison to other technologies |
|
|
|
| Hibernate - Persistance Layer of OnTra™ Technology Framework |
|
| Introduction |
|
In enterprise application development, mostly object-oriented technology such as Java is used to build the application software and relational databases to store the data. However, there is an impedance mismatch between object and relational database technologies. With the object paradigm, we navigate from object to object following relationships that are implemented as object references. Whereas in the relational paradigm, operations are set oriented and relationships are implemented using primary keys and foreign keys as symbolic references. Since the underlying technologies are different, the two technologies do not work together seamlessly, which makes working with object-oriented software and a relational database complex, cumbersome and time consuming in developing enterprise applications. |
|
To overcome this impedance mismatch, there are several popular solutions to persistent data in relational database with Java, such as Java object serialization, JDBC, Enterprise JavaBean and other Persistence Frameworks. The different solutions have different features for enterprise application development. Therefore, it is essential to find an appropriate solution to meet the enterprise application requirements such as performance, flexibility, transaction, scalability and so on. |
|
Hibernate is an open source object-relational mapping framework. Hibernate includes some important differences from JDBC and Enterprise JavaBean. Through analysis, comparisons and experiments, it has been widely reported that Hibernate is a better persistence framework than implementing Enterprise JavaBean or straight JDBC. |
|
| Benefits of Using Hibernate over Entity Beans |
|
The primary benefits of JavaServer Faces technology include: |
|
| |
|
Hibernate Beans are easier to implement since you don't need any interface coding. |
|
| |
|
Queries can be dynamic and perform faster |
|
| |
|
Hibernate offers a more object-oriented approach. You can map is-a relationships as subclasses. |
|
| |
|
For data transfer you can use Hibernate Beans as DTOs if you want (and if it's applicable). You can even fill 'custom' DTOs with query results just with one line of code using the select-new construct. |
|
| |
|
Hibernate will be used as the persistence framework for the OnTra™ Technology Framework . |
