Over a million developers have joined DZone.

Jt5.3 - Java Pattern Oriented Framework

DZone's Guide to

Jt5.3 - Java Pattern Oriented Framework

· ·
Free Resource

Jt5.3 has been released. Jt is a design pattern framework for the rapid implementation of Java applications. Jt implements many well-known patterns including Data Access Objects (DAO), GoF design patterns and J2EE patterns. Jt5.3 features several Enterprise Service Bus components:

  • Enterprise Service Bus Adapter
  • JMS Adapters
  • EJB Adapter
  • Axis Proxy 
  • Restful Web Services
  • Web Services Adapter (Axis)
  • XML/Component conversions

The Jt Enterprise Service Bus implementation allows you to connect heterogeneous applications regardless of the technologies being used, including JMS, Web Services, EJB, REST, HTTP, EJBs, etc.

Jt 5.3  also features a version of the reliable file transfer program (JtRftp). The JtRftp is a reference application built on top of the Jt framework. The JtRftp application allows users to transfer files of any size reliably by taking advantage of the framework Enterprise Service Bus capabilities and components.  The use of JMS and transactions make the file transfer reliable.

The framework addresses the following goals and requirements:

A) The pattern oriented framework implements and 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 possible 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, REST and Axis 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.

For additional information please refer to http://freedom.lunarpages.com/Jt/

Please Post your questions there.

Jt Documentation can be found at http://freedom.lunarpages.com/Jt/Jt.htm


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}