Danev| MFinance| JFW| Mail| MobilePark| HandyFx| TopShop| Dantest     
JFrameworkWeb SearchDownloadNewslettersFirm Profile

  Menu


    What is a Framework
    Framework Objectives
    Developing a Framework

    Architecture
    J2EE App Architecture
    Physical Architecture

    App Building Approaches
    Structuring Web App
    Components Manager
    Object Relational Mapping  

    Online Documentation

    Glossary

    News
    Download
    Message Board
    Contacts

  Summary

  A framework is a set of common and prefabricated software building blocks that programmers can use, extend or customize for specific computing solutions. With frameworks developers do not have to start from scratch each time they write an application. Frameworks are built from collection of objects so both the design and code of the framework may be reused.

 



Summary   
 You Are Here: Home > Summary


Document gives a detailed explanation of JFramework design and defines implementation requirements and rules.

The main aim of JFramework is to define a base, design principles and implementation rules of building portable Internet Java applications. Applications built with JFramework conform Java 2 Enterprise Edition (J2EE) Application Model standards and run on J2EE compatible platforms.

J2EE Application Model is a standard application model for developing multi-tier, thin-client services. It defines three types of application components:

-  Client components (stand-alone programs, applets, standard web browsers). They form the client tier of the application.
Currently JFramework identifies only standard web browsers as clients of JFramework applications;

-  Servlets and JSP pages typically execute in a web server/container and respond to HTTP requests from web clients. Servlets and JSP pages may be used to generate HTML pages that are an application's user interface. They may also be used to generate XML or other data format appropriate for the clients. JSPs implement the presentation logic of the application and lay in its web/presentation tier.
Each JFramework application consists of a single servlet. JFramework design allows other technologies to be used to support the presentation logic instead of JSP;

-  Enterprise JavaBeans™ (EJB) components execute in a transactions supporting environment (EJB container). EJBs implement the business logic of the J2EE application. They form the business tier of the system
JFramework design allows other technologies to be used to support the business logic when no container-managed transaction support is needed. These are Pure Java Class components;

JFramework is designed in the terms of Model-View-Controller design pattern. The Controller and View lay in the presentation logic tier. The Model part corresponds to the business logic tier itself. The core of the Controller part is the Components Manager. It integrates all application components and defines uniform components registration and lookup methods by using a common name space. Components Manager makes JFramework independent from the concrete application logic and concrete application configuration.

The parts of JFramework are encapsulated in certain Java packages. There are a few additional packages to mediate between JFramework and the application components and to support their integration.



©2002 Frontior Technologies. All Rights Reserved.
QWave.com QBioscan.com QSART.com QANS.com QMedical.com AutonomicTest.com QHRV.com QAthlete.com Medeia.com Dantest.com 08.18.17