Jt 2.1: The Pattern Oriented J2EE Framework
Jt is a pattern oriented framework for the rapid implementation of J2EE 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 messages, attributes, logging/debugging capabilities, resource loading, etc. This framework supports several BPM and J2EE technologies including Struts, Java Server Pages (JSPs), AJAX, JDBC, EJBs, JMS, JavaMail, XML and Web Services.
Jt2.1 features several enhancements to the Jt components and a version of the JtWizard web application. This demo application is based on the Jt framework.
Additional features include:
- Jt implements many well-known design patterns. This includes Data Access Objects (DAO), adapters for several J2EE APIs, Gang of Four (GoF) design patterns and J2EE patterns.
- Jt implements a messaging pattern/API: framework objects are able to interchange information and perform computations by sending, receiving and processing messages. The messaging paradigm provides provides stronger encapsulation and looser coupling..
- Implemented J2EE design patterns include J2EE business delegate, J2EE Session Facade, J2EE Service Locator and J2EE Value Object.
- The framework can be easily extended by implementing additional Jt adapters and helpers.
- 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.
- Support for 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.
- 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 helpers and built-in bean/XML mapping capabilities.
- 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 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.
- Integration with the asynchronous Java Message Service (JMS). Jt messages can be sent and received via JMS adapters.
- Cross-platform, implemented using JavaTM technology.
- Integration with the Eclipse environment.
- Runs on any J2EE 1.4 compatible application server.
Jt online documentation can be found at http://www.fsw.com/Jt/Jt.htm
For additional information please refer to http://jt.dev.java.net
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)