Jt7.0 has been released.
Jt is a design pattern framework for the rapid implementation of Java and Android applications. Jt implements many well-known patterns including Data Access Objects (DAO) and GoF design patterns.
The framework addresses the following goals and requirements:
A) The design pattern framework implements and/or facilitates the implementation of well-known design patterns like GoF 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 (MDP): 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 Android, BPEL, 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). The main Jt functionality is able to run on smartphones under Android.
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 the following URLs:
a) Java Pattern Oriented Framework, An application of the Messaging Design Pattern
IBM Technical Library
b) Messaging Design Pattern (MDP) and pattern implementation -
Published in the 17th conference on Pattern Languages of Programs (PLoP 2010).
- Posted by: Dan Evans
- Posted on: November 09 2010 08:33 EST
Jt7.0 has been released.
- Jt7.0 - Java Design Pattern Framework for Android by shawn spencer on November 09 2010 14:15 EST
- Jt7.0 - Java Design Pattern Framework for Android by Dan Evans on November 12 2010 10:20 EST
1. Good programmers authomatically use good patterns. Lets use the word "framework" for "patterns".
2. you dont want to add extra jars etc of your "framework" on the phone. Phone memory etc is already small.
3. I knew it was IBM post as soon as i saw a ESB in there. Why is ESB sold so hard by IBM now a days. Are you not meeting your numbers ? Every presentation , conference i go to which has IBM in it has ESB in it.
you may want to get familiar with the framework and related technical papers in order to see the advantages.
the whole framework is around 500K (one jar/minimum overhead). Small size is not an issue. This framework can run on Android as well as it does on high-end servers.
"The framework is designed to be lightweight and fast in terms of performance (low overhead/small signature)."
This work doesn't come from IBM. They published the Article about the design pattern framework.
BTW, I forgot to mention, Android is also in need of good pattern implementations based on our experience (DAO, etc). For instance, JDBC is OK but it is far from ideal. The Jt Pattern Framework can meet this need.
ESB is part of SOI inside the SOA. As you know the SOA nowadays is hype and companies like IBM or oracle are trying to push everyone into it and extend the hype to grab more wealth :)
But whenever I found integration problem, i used Mule or Spring integration and it resolved my issues very well.
Mule is an ESB/SOA implementation. I don't think it supports Android at the moment. A very light framework is required. I may be wrong.