Jt - Java Pattern Oriented Framework (Jt 4.2)


News: Jt - Java Pattern Oriented Framework (Jt 4.2)

  1. Jt - Java Pattern Oriented Framework (Jt 4.2) (3 messages)

    Jt4.2 has been released. 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. Jt4.2 features several enhancements to the Jt components and a version of the Jt Portal (JtPortal). The Jt Portal is a reference web application implemented using the Jt framework. Jt4.2 also features portal components and capabilities: - Account and Profile management - Mailing list capabilities - Photo upload capabilities - Product management - Shopping Cart - Credit card payment via Paypal adapter - Security/Role capabilities - Forum Module DAO enhancements include: - Automated generation of database keys - Support for complex queries and join operations 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 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. For additional information please refer to http://freedom.lunarpages.com/Jt/

    Threaded Messages (3)

  2. Awesome, I can't wait to migrate to 4.2!
  3. shit[ Go to top ]

    this is your MailingList component? coupled with Struts: import org.apache.struts.action.ActionForm; /** * Sends email to the members of a mailing list. * Runs in a separate thread. */ public class MailingList extends JtThread { do you know what means patterns? what is Pattern Oriented Framework? I only find some code example with GOF, no DI, No AOP, only have a Factory.
  4. Is this "framework" a joke? The whole idea of patterns is that they are general solutions to your bespoke domain. How can JT implement these patterns for you? Every post on the JT "framework" has exactly the same working and it seems to come from some dodgy consultancy.