Re: Jt Pattern Oriented Framework (looking for champion/mentors)
Hi folks, I've updated the proposal with names: http://wiki.apache.org/incubator/JtPatternFrameworkProposal I'll need to update the page again since a couple of people joined the project recently. Regards, Edgar P.S. Jt 2.7 has been released. 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. Main Features - Implemented J2EE design patterns include J2EE business delegate, J2EE Session Facade, J2EE Service Locator and J2EE Value Object. - 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. - 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 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. - Integration with the XML APIs via XML adapters, 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
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
I'll update the project proposal with names as soon as I get the chance. As explained in the proposal, we plan to move the project to a central location. Some of the internal project info/documentation (email, etc) is scattered around. The main focus/goal has been completing the core functionality of the pattern oriented framework. Regards, Ed --- On Tue, 7/22/08, Roland Weber [EMAIL PROTECTED] wrote: From: Roland Weber [EMAIL PROTECTED] Subject: Re: Jt Pattern Oriented Framework (looking for champion/mentors) To: general@incubator.apache.org Date: Tuesday, July 22, 2008, 4:22 AM David S (or rather Ed) wrote: Community 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 you already have an active community of users and contributors? Any public record of that? Names and/or numbers?
RE: Jt Pattern Oriented Framework (looking for champion/mentors)
Hi folks, We've put together a draft proposal for the Jt pattern Oriented Framework. I hope it answers some of the questions regarding project status, community, licensing, etc. Regards, Ed 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. Criteria Current Status The current release of the framework (2.6) meets most of the goals outlined above. Item F is still work in progress. The software base is very stable (production quality). Several production applications have been built based on the Jt framework. Documentation, reference framework applications and examples are available. Meritocracy Meritocracy will be fostered and encouraged within the project. We will follow the guidelines of the Apache Software Foundation. Community contributions and feedback are always welcome.We also plan to actively encourage individuals to get involved in the project and be recognized based on Merit. Community 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. We plan to open the project to a wider audience in order to achieve a larger and more diverse community. Alignment Jt is aligned well with existing Apache projects and technologies. The framework has been integrated with several Apache technologies including Struts (MVC design pattern) and Axis (Web Services Adapter). The Jt automated Wizard capabilities has also been built based on Apache products. Known Risks Orphaned products: The projects has been
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
David S (or rather Ed) wrote: Community 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 you already have an active community of users and contributors? Any public record of that? Names and/or numbers? Orphaned products: The projects has been growing as an open source project for several years. The team is committed to continue this work therefore the risk is fairly small. Names or numbers on the team? Public records of the growing? The CVS mails show no relevant activity before October 2007, nor afterwards. Homogenous developers: The people involved with the project work for several organizations who are geographically distributed across the world. The only account used on the project site is wwwfswcom, an obvious reference to a website that seems to belong to a software consulting company. Can you give some details on distributed across the world? Number of people by country or continent, for example? Reliance on salaried developers: This project does not rely on salaried contributors. They work on a volunteer basis. Is the above mentioned software consulting company aware of the fact that a diverse team of volunteers is indirectly referencing its website when releasing open source software? Project information and complete documentation/sources can be downloaded from http://jt.dev.java.net/. java.net forums and mailings lists are not used. So which forums and/or mailing lists do you use? As far as I can see you didn't use the CVS repo either, except for index.html and one drop of code in October 2007. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
On Fri, Jul 18, 2008 at 11:24 AM, David S [EMAIL PROTECTED] wrote: Hi Eelco, The project site contains mainly technical/download information. We haven't been using it for anything else (mailing list, forums, etc). Where then??? You will soon notice that we care more about the community, then probably licensing difficulties and lastly the codebase itself. Also, *I* am particularly concerned over David S sending mail, 'signed' Edgar... Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
a cursory assessment... License currently is LGPL. CVS history goes back to August 2006. All commits by wwwfswcom. Not a single message on the dev list. Not a single posting in the forum. Looks like a case of open source, closed development. On the plus side, changing the license shouldn't be a problem. cheers, Roland https://jt.dev.java.net/servlets/ProjectMailingListList https://jt.dev.java.net/servlets/SummarizeList?listName=cvsby=author https://jt.dev.java.net/servlets/SummarizeList?listName=dev https://jt.dev.java.net/servlets/ProjectForumView - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
Hi Ed, Judging from http://jt.dev.java.net/, there is one active person on the project, and now discussion or other signs of community whatshowever. Wouldn't it be a good idea to start building up a community on that site first? Regards, Eelco On Wed, Jul 16, 2008 at 8:19 PM, David S [EMAIL PROTECTED] wrote: Hi folks, Our project (Jt Pattern Oriented Framework) is interested in joining the ASF incubator. After getting familiar with the incubator policies and procedures, we are looking for people interested in becoming a champion or a mentor. We hope to learn more about ASF and pursue the proposal process. Additional information about this Open Source project can be found at http://jt.dev.java.net/ The framework should address the following goals: A) The pattern oriented framework should implement and/or facilitate the implementation of well-known design patterns like GoF design patterns and J2EE Design patterns. The framework itself should be conceived and implemented based on design patterns (from the ground up). The framework should also facilitate and accelerate the implementation of applications based on design patterns. B) The framework architecture should be based on a messaging design pattern: framework objects should be 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 should take full advantage of the power and simplicity of the messaging design pattern. C) The framework lego/messaging architecture should provide transparent access to remote components: remote framework objects should be treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) should make this posible by hiding the complexities associated with remote APIs. D) The framework should provide 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 should be 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 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 applications to be generated directly from the UML design diagrams. G) The framework messaging architecture should facilitate testing and debugging efforts. The framework should provide 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 should be integrated with open source IDEs. Thanks in advance for your feedback and suggestions. I look forward to hearing from you. Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
Hi Eelco, The project site contains mainly technical/download information. We haven't been using it for anything else (mailing list, forums, etc). We believe the Apache incubator would be a better venue for building community. Everyone interested in contributing is welcome. On the other hand the framework is probably one of the few pattern oriented frameworks (especially open source). The framework (version 2.6) has also been used as part of several production applications. Regards, Edgar --- On Thu, 7/17/08, Eelco Hillenius [EMAIL PROTECTED] wrote: From: Eelco Hillenius [EMAIL PROTECTED] Subject: Re: Jt Pattern Oriented Framework (looking for champion/mentors) To: general@incubator.apache.org Date: Thursday, July 17, 2008, 7:41 AM Hi Ed, Judging from http://jt.dev.java.net/, there is one active person on the project, and now discussion or other signs of community whatshowever. Wouldn't it be a good idea to start building up a community on that site first? Regards, Eelco On Wed, Jul 16, 2008 at 8:19 PM, David S [EMAIL PROTECTED] wrote: Hi folks, Our project (Jt Pattern Oriented Framework) is interested in joining the ASF incubator. After getting familiar with the incubator policies and procedures, we are looking for people interested in becoming a champion or a mentor. We hope to learn more about ASF and pursue the proposal process. Additional information about this Open Source project can be found at http://jt.dev.java.net/ The framework should address the following goals: A) The pattern oriented framework should implement and/or facilitate the implementation of well-known design patterns like GoF design patterns and J2EE Design patterns. The framework itself should be conceived and implemented based on design patterns (from the ground up). The framework should also facilitate and accelerate the implementation of applications based on design patterns. B) The framework architecture should be based on a messaging design pattern: framework objects should be 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 should take full advantage of the power and simplicity of the messaging design pattern. C) The framework lego/messaging architecture should provide transparent access to remote components: remote framework objects should be treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) should make this posible by hiding the complexities associated with remote APIs. D) The framework should provide 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 should be 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 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 applications to be generated directly from the UML design diagrams. G) The framework messaging architecture should facilitate testing and debugging efforts. The framework should provide 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 should be integrated with open source IDEs. Thanks in advance for your feedback and suggestions. I look forward to hearing from you. Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jt Pattern Oriented Framework (looking for champion/mentors)
Noel, We plan to prepare a preliminary proposal that should address many of these questions (technical state, membership, interfaces with other technologies, etc). I'll send it to the mailing list for discussion as soon as possible.. I can tell you that the current version of the framework meets many of the original design goals (should, will). It is a version 2.5 (fairly mature software base). Actually there are several production applications that have been built on top of this pattern oriented framework. We look forward to having this discussion. Regards, Edgar --- On Thu, 7/17/08, Noel J. Bergman [EMAIL PROTECTED] wrote: From: Noel J. Bergman [EMAIL PROTECTED] Subject: RE: Jt Pattern Oriented Framework (looking for champion/mentors) To: general@incubator.apache.org Date: Thursday, July 17, 2008, 3:22 PM David Sheppard wrote: Our project (Jt Pattern Oriented Framework [http://jt.dev.java.net/]) is interested in joining the ASF incubator. After getting familiar with the incubator policies and procedures, we are looking for people interested in becoming a champion or a mentor. We hope to learn more about ASF and pursue the proposal process. As you can see, several people have already taken a look at the project, each from their own perspective. I, for example, looked at it last night, and wondered how it would tie into/relate with Ode, Tuscany, and other similar/related ASF projects, given the emphasis on messaging, BPM, etc. Can you tell us more about who is currently involved, and the current technical state of the project (q.v. a number of the statements in the proposal were phrased as will and should)? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jt Pattern Oriented Framework (looking for champion/mentors)
Hi folks, Our project (Jt Pattern Oriented Framework) is interested in joining the ASF incubator. After getting familiar with the incubator policies and procedures, we are looking for people interested in becoming a champion or a mentor. We hope to learn more about ASF and pursue the proposal process. Additional information about this Open Source project can be found at http://jt.dev.java.net/ The framework should address the following goals: A) The pattern oriented framework should implement and/or facilitate the implementation of well-known design patterns like GoF design patterns and J2EE Design patterns. The framework itself should be conceived and implemented based on design patterns (from the ground up). The framework should also facilitate and accelerate the implementation of applications based on design patterns. B) The framework architecture should be based on a messaging design pattern: framework objects should be 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 should take full advantage of the power and simplicity of the messaging design pattern. C) The framework lego/messaging architecture should provide transparent access to remote components: remote framework objects should be treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) should make this posible by hiding the complexities associated with remote APIs. D) The framework should provide 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 should be 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 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 applications to be generated directly from the UML design diagrams. G) The framework messaging architecture should facilitate testing and debugging efforts. The framework should provide 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 should be integrated with open source IDEs. Thanks in advance for your feedback and suggestions. I look forward to hearing from you. Ed
