incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "JtPatternFrameworkProposal" by dsheppard2k
Date Mon, 04 Aug 2008 01:11:36 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by dsheppard2k:

New page:
'''Jt Proposal'''

Project Name: Jt Pattern Oriented Framework

== Introduction ==

This proposal describes a Pattern Oriented Framework for the rapid implementation
of Java applications. This integrated framework is based on a messaging architecture
which provides strong encapsulation and loose coupling; framework components can be 
interchangeably plugged into complex framework applications using a “Lego" approach. 
This framework provides capabilities for the implementation of applications 
based on design patterns. The framework itself is conceived, from the ground up, 
based on design patterns. Jt is probably one of the first Pattern Oriented Frameworks
(open source).

=== Goals ===

The framework addresses the following goals:

A) The pattern oriented framework implements and/or facilitates the implementation of
well-known design patterns like Gang Of Four design patterns (GoF) and J2EE Design patterns.
The framework itself  is conceived and implemented based on design patterns (from the ground
up). The framework also 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 interchangeably 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/API.

C) The framework lego/messaging architecture provides transparent access to remote components:
remote framework objects are 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,  Data Access Object implementations (DAO), Model View Controller implementations (MVC),
EJBs, AJAX, JMS, XML and Web Services. 

E) The framework is designed to be lightweight and fast (low overhead/small footprint).

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. The framework
should provide 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 application modules to be generated directly from the UML design diagrams.
This goal is still work in progress. There is an early version of the Jt Wizard. 

G) The framework  messaging architecture facilitates testing and debugging efforts.
It provides capabilities for testing components as independent units by
sending messages to the component and verifying the expected reply messages.
H) In order to provide additional productivity, the framework has been integrated
with open source IDEs.

== Current Status and Community ==

There are several people involved with the project. The software base is very stable.
Several production quality applications has been built based on the Jt framework.
One of the next objectives is to continue growing an active community of 
users and contributors. It is expected that community will continue to grow.
So far the main focus has been the completion of the core framework functionality. 
We see Jt becoming an ASF incubator project as a next step in its evolution.

==== Meritocracy ====

Meritocracy will be fostered and encouraged within the project. We will follow the guidelines
the Apache Software Foundation. Community contributions and feedback are always welcome.
We also plan to actively encourage individuals to get involved in the project.

==== Alignment ====

==== Core Developers ====

==== Orphaned products ====

==== Inexperience with open source ====

==== Homogeneous developers ====

==== Reliance on salaried developers ====

==== No ties to other Apache products ====

==== A fascination with the Apache brand ====


== 1. Project Scope ==



== 3. ASF Resources Requested ==

=== 3.1 Mailing lists ===

=== 3.2 Revision Control System ===



=== Champion ===

=== Mentors ===

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message