Welcome to the Java Pattern Oriented Framework

Overview

Jt is a pattern oriented framework for the rapid implementation of Java applications. Jt has been utilized in several large mission critical systems. Jt implements many well-known patterns including Data Access Objects (DAO), GoF design patterns and J2EE patterns.

Jt features several enhancements to the Jt components and a version of the Jt automated Wizard (JtWizard). The Jt Wizard is an application built on top of the Jt framework that provides automated capabilities for generating framework applications. The Jt Wizard is able to automatically generate application modules based on several design patterns including Jt Messaging, DAO, MVC and GoF. The current Jt Wizard implementation provides integration with MVC Struts and DAO Hibernate. DAO mapping files, Struts configurations files, Views (JSPs), Java classes are automatically built by the Jt Wizard. The Jt Wizard is also a reference web application implemented using the Jt framework.

The framework addresses the following goals and requirements:

A) The pattern oriented framework implements and/or facilitates the implementation of well-known design patterns like GoF design patterns and J2EE Design patterns. The framework itself is conceived and implemented based on design patterns (from the ground up). The framework facilitates and accelerates the implementation of applications based on design patterns.

B) The framework architecture is based on a messaging design pattern: framework objects are able to interchange information and perform computations by sending, receiving and processing messages. A messaging API provides strong encapsulation and loose coupling; framework components can be easily plugged into complex framework applications using a “lego/messaging” architecture. The framework takes full advantage of the power and simplicity of the messaging design pattern.

C) The framework lego/messaging architecture provides transparent access to remote components: remote framework objects is treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) make this posible by hiding the complexities associated with remote APIs.

D) The framework provides transparent integration with other technologies via framework adapters, proxies and the implementation of related design patterns. These technologies include BPM, DAO implementations, MVC implementations, EJBs, JMS, XML and Web Services.

E) The framework is designed to be lightweight and fast in terms of performance (low overhead).

F) The framework messaging/lego architecture should improve and simplify design/development efforts. There should be a tight correspondence between UML design diagrams and the framework messaging based applications and components needed for the implementation. Ideally, the framework provides wizards and automated capabilities for generating framework applications. Framework components should be easily added to BPM process diagrams. In future versions of the framework, it should be possible for applications to be generated directly from the UML design diagrams.

G) The framework messaging architecture facilitates testing and debugging efforts. The framework provides capabilities for testing components independently (each component as a unit) by sending messages and verifying the reply (output) messages.

H) In order to provide additional productivity benefits, the framework is integrated with open source IDEs.

Features



* Implemented J2EE design patterns include J2EE business delegate, J2EE Session Facade, J2EE Service Locator and J2EE Value Object.

* Web Services integration via the implementation of Web Services adapters and proxies. The Jt messaging API greatly simplifies the development and deployment of web services.

* Integration with business process modeling (BPM). A jBPM adapter is provided within the Jt framework. jBPM is an open source implementation of the BPM technology. A Jt application can now be modeled using a process graph. This provides users with a very powerful way of modeling business processes.

* Integration with the MVC (Model View Controller) design pattern and Ajax. Universal Jt components and adapters provide a transparent interface between the Jt framework API and these technologies. The business logic (controller piece) can be implemented using Jt framework components and/or BPM business processes.

* Integration with the Hibernate implementation of Data Access Objects (DAO). A Jt adapter provides a transparent interface between the Jt framework and Hibernate DAOs. A native Jt DAO implementation is also provided. Additional DAO strategies can be easily plugged in.

* JDBC integration via a JDBC adapter.

* The Command pattern implementation supports a request log, a queueing mechanism and undoable operations.

* JavaMail API integration via the implementation of a JavaMail adapter.

* Integration with J2EE Enterprise Java Beans (EJBs) via Jt Adapters and proxies. EJB clients are able to gain transparent access to remote framework objects. No need to deal with the complexities of EJB application development. An implementation of the J2EE Service Locator pattern is also provided.

* Easy customization of framework applications. This is done via resource files: object attributes can be automatically loaded from a resource file.

* Java Server Pages (JSP) integration.

* Integration with the XML APIs via XML adapters, helpers and built-in bean/XML mapping capabilities.

* Integration with the asynchronous Java Message Service (JMS). Jt messages can be sent and received via JMS adapters.

* Built-in logging/debugging capabilities. Messages between framework objects are automatically logged. This simplifies the debugging and testing tasks.

* Built-in testing capabilities.

* Efficient and lightweight in terms of memory utilization.

* The framework can be easily extended by implementing additional Jt adapters and helpers.

* The Jt Framework provides a consistent way of handling and logging application messages, errors and exceptions.

* Proven technology. The Jt framework has been used for the development of several large enterprise applications.

* Cross-platform, implemented using JavaTM technology.

* Integration with the Eclipse environment.

* Runs on any J2EE compatible application server.

Download and Installation


To download and install Jt , follow these simple steps:

1. Download the latest distribution of Jt. The distribution includes installation instructions, the Jt user’s manual and the Jt API documentation.


Build Instructions

To build the Jt Framework, follow these steps:

1. Download the framework sources.

2. Include the third-party jars required by the framework. The installation instructions found in the distribution explain what packages and jar files are required.

3. You can either use an IDE or ant. Under Eclipse, a project can be easily created. Under ant, run ‘ant dist’.

Usage Instructions

To use Jt, build the application or download a precompiled binary, and make sure you can run it. Then, follow the instructions included in the Jt user’s manual and the Jt API documentation.

Support

Jt is a community-supported open-source product. You can get support by sending technical questions to jtowner@dev.java.net or subscribing to the Jt mailing list.Please review the documentation before sending your technical questions.

Participation

Additional contributors are welcome. We are looking for software engineers and QA folks to build and test additional applications and adapters based on the Jt framework. We are also looking for folks to write technical articles and tutorials about the framework.

Please send us your software, Jt components and/or success stories based on the Jt Framework. We'll feature them on our project page.

Getting Started

If you want to begin right away, go the Jt documentation and get started.

Revision History

- Jt 1.1 - [8/15/06]
Open source release to java.net.

- Jt 1.2 - [9/01/06]
Enterprise Java Bean (EJB) support.

- Jt 1.3 - [10/01/06]
Completion of Gang of Four (GoF) design patterns.

- Jt 1.4 - [11/01/06]
Main J2EE Design patterns.

- Jt 1.5 - [12/01/06]
JMS integration.

- Jt 1.6 - [04/01/07]
BPM integration.

- Jt 1.7 - [09/01/07]
MVC/Struts and Ajax integration.

- Jt 1.8 - [10/01/07]
Hibernate DAO integration.

- Jt 1.9 - [11/01/07]
XML integration enhancements.

- Jt 2.0 - [10/01/07]
Logging and documentation enhancements.
Proxy enhancements.
Eclipse integration.

- Jt 2.1 - [02/01/08]
Enhancements to the Jt components.
Early version of the automated Wizard (JtWizard)

- Jt 2.2 - [03/01/08]
Ongoing work on automated Wizards.

- Jt 2.3 - [04/01/08]
JDOM adapter and ongoing work on automated Wizards.

- Jt 2.5 - [05/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)

- Jt 2.6 - [06/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)

- Jt 2.7 - [07/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)

- Jt 2.8 - [09/01/08]
Enhancements to the native Jt DAO implementation.
Ongoing work on automated Wizards (JtWizard)

- Jt 2.9 - [10/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)

- Jt 3.0 - [11/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)

- Jt 3.1 - [12/01/08]
Enhancements to the Jt components.
Ongoing work on automated Wizards (JtWizard)