 |
Assembling reusable UI components in a page |
|
|
Connecting these components to an application data source |
|
|
Wiring client-generated events to server-side event handlers |
|
| JSF Advantages & Highlights |
|
| We recommend JSF framework for the following reasons: |
|
|
New framework with enhanced capabilities (like Navigation, Validators, On Change controllers etc) |
|
|
Access to source code |
|
|
Extensible |
|
|
Custom tag libraries |
|
|
Internationalization |
|
| The design and the technology's highlight of JSF and its advantages are described below. |
|
|
Separation Of Concerns makes development easier as a module will concentrate on one or a related set of responsibilities only. Maintenance of/extending such modules are easier. |
|
|
Layering of the application based on responsibilities and by using design patterns and frameworks to solve common problems and infrastructure issues. |
|
|
The JSF architecture based applications has the following layers - |
|
| |
» |
A Presentation layer, JSF Design Framework. |
|
| |
» |
A Services layer, independent of presentation, exposing the business services. |
|
| |
» |
A Data store independent persistence layer, acting as a bridge between the data store and business logic. |
|
|
|
Model View Control (MVC) separates presentation logic, control flow logic and business logic. |
|
|
Java Beans is used for implementation of business logic and Hibernate to be used for Data Objects. |
| |
| Architectural Highlights |
|
 |
| |
| The recommended design pattern will allow: |
|
|
Easier development |
|
|
Easier Maintenance/extendibility of module |
|
|
Horizontal Scalability on all layers (Presentation, Application & Data) |
|
|
Open Standard Conformity (Easier support, Maintain & Migration capability) |
|
|
Cost Effective technology (Upfront and Ongoing costs) |
|
| Benefits of Java Server Faces (JSF) |
|
|
The primary benefits of Java Server Faces technology include: |
|
|
Ease-of-Use: Several aspects of the Java Server Faces architecture contribute to its ease-of-use. For one, Java Server Faces technology offers a clean separation between logic and presentation, enabling a wide range of users -- from web-page designers to component developers-- to take advantage of Java Server technology, resulting in a division of labor and a shorter development cycle. Also, a user-interface created with Java Server Faces technology handles all the complexities of user-interface management, including input validation, component-state management, page navigation, and event handling. |
|
|
Standardization: Java Server Faces technology is being 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 Java Server Faces technology in their tools. |
|
|
Device Independence: Java Server Faces technology is designed to be flexible. By defining only component functionality in extensible UI component classes, the Java Server Faces architecture allows component developers to extend the component classes to generate their own component tag libraries targetted for specific clients. |
|
|
Deployment: JSF technology enables the interfaces to be deployed over other devices like mobile with very few changes. |
|
| JSF - UI benefits |
|
| ANMsoft proposes to use the JSF framework for building user interfaces for business applications. whi ch 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 Java Server Pages (JSP) custom tag library for expressing a Java Server Faces interface within a JSP page. |
| |
| Hibernate-Persistence Framework |
| |
| In current enterprise application development, people mostly use object-oriented technology such as Java 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. |
| |
| Advantages of Hibernate over Entity Beans: |
|
|
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 shopping platform development. |
| |
