[cvs] expresso commit by scann: Updated the upcoming releases as a
point of
JCorporate Ltd
jcorp at jcorporate.com
Mon Jan 24 02:01:39 UTC 2005
Log Message:
-----------
Updated the upcoming releases as a point of discussion; and so that we have something for the 5.6 release announcement.
Modified Files:
--------------
expresso/expresso-web/expresso/doc:
roadmap.html
Revision Data
-------------
Index: roadmap.html
===================================================================
RCS file: /home/javacorp/.cvs/expresso/expresso/expresso-web/expresso/doc/roadmap.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -Lexpresso-web/expresso/doc/roadmap.html -Lexpresso-web/expresso/doc/roadmap.html -u -r1.27 -r1.28
--- expresso-web/expresso/doc/roadmap.html
+++ expresso-web/expresso/doc/roadmap.html
@@ -11,231 +11,182 @@
<META http-equiv="Content-Style-Type" content="text/css">
<link href="style/default.css" rel="stylesheet" type="text/css">
</HEAD>
-<BODY vlink="#0000FF" alink="#000000" bgcolor="#FFFFFF" text="#000000" link="#0000FF">
-<DIV align="left">
- <TABLE border="0" cellpadding="0" cellspacing="0" width="100%">
- <TBODY>
- <TR>
- <TD valign="top">
- <h1 align="center"><A name="Top">Expresso 5.x Road Map</A></h1>
- <p class="jc-explanation">This document contains a high-level overview
- of the development work currently underway in Expresso, and a list
- of what features are expected in what release in the near future.
- By it's very nature, this information may change frequently, so check
- back about once a month.</p>
- <TABLE border="0" width="100%">
- <TBODY>
- <TR>
- <TD valign="top">
- <H4>Version:</H4>
- </TD>
- <TD valign="top">
- <P class="jc-default">As of Expresso 5.5</P>
- </TD>
- <TD valign="top">
- <H4>Maintainer:</H4>
- </TD>
- <TD valign="top">
- <P class="jc-default"><A href="mailto:scann at jcorporate.com?Subject=Expresso prerequisites">Sandra
- Cann</A></P>
- </TD>
- </TR>
- </TBODY>
- </TABLE>
- <h2>Introduction</h2>
- <P><span class="jc-default">This document is intended to provide an
- overview of planned features in upcoming Expresso releases. As
- such the <B> below list of features to be added does NOT take into
- account many contributions from community developers.</B> Open
- source is driven by the needs of the community and hence developers
- will contribute additional features based on what they needed for
- their own development. The benfit of contributing is the developer
- stays with release product and their contributions are then enhancemend
- and improved upon by the community brainshare.<BR>
- <BR>
- We'd like to encourage contributors to document their code changes
- as part of the contribution. Also think about J2EE design patterns
- and aim to create a more flexible framework, specifically more decoupling
- between its parts and creating documentation to faciliate understand
- functionality and Expresso's design patterns. If/when possible we'd
- also like to see UML diagrams about various aspects of the framework,
- as well as a "large view" collaboration diagram for the
- components that make up the overall architectural framework. </span>
- <P><span class="jc-default">Please also see: </span>
- <OL>
- <LI><span class="jc-default"><A href="http://www.jcorporate.com/html/customers/developers/releasemgmt.html" target="_blank">Release
- Management</A> document </span>
- <LI><span class="jc-default">"<A href="http://www.jcorporate.com/expresso/components/internal/tasks.jsp?project=EXPRESSO" target="_blank">Task
- List</A>" for an up-to-date listing of the current development
- tasks and team member assignment. </span>
- <LI><span class="jc-default">If you'd like to volunteer for one of
- the below tasks please let us know at <A href="mailto:support at jcorporate.com?Subject=Would like to work on item in task list">support at jcorporate.com</A>. </span>
- </OL>
- <h2>Release 5.x</h2>
- <p class="jc-default">The basic direction of 5.X is to continue to
- include any changes that can be added in without drastically changing
- the available API. Programmers should only require minor changes
- to update from one version to another. So this will cover:</p>
- <UL>
- <LI><span class="jc-default">Bug Fixes </span>
- <LI><span class="jc-default">Performance Improvements </span>
- <LI><span class="jc-default">I18N Improvements </span>
- <LI><span class="jc-default">Largely backwards compatible feature
- additions. (a current example of this is the SSL->NonSSL->SSL
- transition framework that was added) </span>
- </UL>
- <p class="jc-default">Some current ideas on the Expresso 5.X wish list
- include:</p>
- <UL>
- <LI><span class="jc-default">Allow each schema to define it's own
- valid values for the setup table. Thus many items on the setup
- table could simply be drop down boxes. </span>
- <LI><span style='color:red'>[experimental] </span><span class="jc-default">Pluggable look and feel. Stylesheets
- should be at least switchable through the setup table, and perhaps
- if the webadmin wishes to allow it, switchable through the user
- preferences. </span>
- <LI><span class="jc-default">Get rid of frame.jsp and replace it
- with tiles layouts. </span>
- <LI>
- <span style='color:red'>[experimental]</span> <span class="jc-default"> DBConnectionPools to get jndi-based JDBC connections. This will allow
- Expresso integration with JTA
- if the developer so wishes. </span>
- <LI><span class="jc-default">Convert each API or component area into service-oriented architecture (like JMX).</span>
- </UL>
- <P class="jc-default">These are just a few ideas for example stake.
- In the opensource world, many people come up with many fantastic
- ideas that can work well in the current framework.</P>
- <HR>
- <h2>Release 5.0.x [previous stable release]</h2>
- <p class="jc-default">This release will not be maintained since a "new stable" release exists.
- Hence no further features will be added to 5.0.</p>
-
- <hr>
- <h2>Release 5.5 [Current stable release]</h2>
- <p class='jc-default'>Release 5.5 started towards the goal of a basic service-oriented architecture,
- much in the way that JBoss has a microkernel architecture surrounded by MBean services.
- Other releases were skipped due to the Struts integration and many other improvements.
- This release has been through many early access releases and has been reguarded as stable for a long time.</p>
-
- <UL>
- <li><span class="jc-default" style='color:red'>A critical security fix has been recently addressed that allowed SQL injection attacks! </span>
- </UL>
-
- <p class="jc-default">Here is a list of features that has been implemented. <BR>
- </p>
- <UL>
- <li class="jc-default"><b>Struts 1.1 integration.</b><br>
- Fully support Struts 1.1 and includes many JSTL capabilities.
- <li class="jc-default"><b>Performance Improvements.</b><br>Pattern matching, caching, and available memory improvements.
- <li class="jc-default"><b>Memory leaks fixed.
- <li class="jc-default"><b>Internationalization (I18N).</b><br>
- Chained message bundles and changing locales occurs instantly
- <li class="jc-default"><b>Database connections improved.</b><br>
- DBCreate fixes, multiple SQL injection fixes, 'IS NULL' and 'IS NOT NULL' support, JoinedDBObjects more robust, SQL where clause better supported in JoinedDBObjects, deleteAll respects where clauses
- <li class="jc-default"><b>Remove Deprecated Functions all together.</b><BR>
- There are a number of functions that have been marked @deprecated
- since version 4.0. These will be removed and all functions
- calling them will be recoded so that they are no longer calling
- the @deprecated functions.
- <li class="jc-default"> <b>Clean up all JavaScript warnings</b><BR>
- Recheck the pages to make sure no JavaScript warnings are happening. </li>
- <li class="jc-default"><b>Componentization</b>: Try componentize
- a couple of services in Expresso under this new scheme as proof
- of conept. Specifics right now are planned to be Cache and Logging. </li>
- <li class="jc-default"> <B> Update ConfigManager</B> <b>and refactor
- for for better component orientation</b><BR>
- Include a service manager and allowing each component to recognize
- it's own setup values. </li>
- <li class="jc-default"><b>Common Interface for DBObjects/MultiDBOBject</b><br>
- DataObject should be fleshed out so that DBObject and MultiDBObject
- can reside under the same object and DBMaint can work for both. </li>
- <li class="jc-default"><b>Many More</b><br>A couple dozen other BIG improvements - check out the changelog!
- </UL>
-
- <li><span class="jc-default">Bug Fixes </span>
- <ul>
- <li><span class="jc-default">If a bug is considered critical,
- then it should go into the 5.5 code base immediately even
- if it could be potentially higher risk as to causing regression
- errors (and 5.6). </span>
- <li><span class="jc-default">Any other bugs that are 'high risk'
- or require a significant structural change that aren't critical
- should go into the 5.6 code base. </span>
- <li><span class="jc-default">NO Schema Changes, no new features and
- no minor bugs in 5.5.x releases.</span>
- </ul>
- </ul>
- <HR>
-
-
-
- <h2>Release 5.6 - 5.9 direction</h2>
- <p class="jc-default">Our goal is to have updated security interfaces
- to allow for better integration into other J2EE Environments. Here
- is a list of features that is our currrent goal: </p>
- <ul>
- <li class="jc-default"><b>Updated DBMaint User Interface</b><BR>
- Our goal here is to prototype and publish and updated and new modern
- look to DBMaint. </li>
- <li class="jc-default"><b>Create DAO Query Object</b><br>
- Data objects need to have the QueryObject fully implemented for
- JDBC. </li>
- <li class="jc-default"><strong>I18N Improvements </strong> </li>
- <li class="jc-default"><B>Component Manager</B><BR>
- Expresso needs the ability to 'deploy' components into the appropriate
- location. So you can install and uninstall components at will
- into your development environment. </li>
- <li class="jc-default"><b>Continued Componentization:</b> Continue
- to componentize other systems in Expresso as time allows. </li>
- <li class="jc-default"> <b>JAAS Integration</b><BR>
- checkLogin() and Login needs to be fully integrated with JAAS so
- that we can better support integration with Application services.<br>
- </li>
- <li class="jc-default"><b>Security Manager Factory</b><BR>
- com.jcorporate.expresso.core.security.SecurityManagerFactory needs
- to be implemented that will construct the appropriate permissions
- for each system. We also need a security manager to help centralize
- security checks.<br>
- </li>
- <li class="jc-default"><b>UserRole Interface</b><BR>
- UserGroups needs to be abstracted into an interface </li>
- <li class="jc-default"><b>Native DataField Types</b><br>
- We need DefaultDataField to be able to support natively multiple
- data types. For example, we need it to be able to support Dates
- natively while converting back and forth so we can reduce CPU
- time. </li>
- <li><span class="jc-default"><b>Continued Componentization:</b> Continue
- to componentize other systems in Expresso as time allows. </span></li>
- </ul>
- <HR>
- <h2>Release 6.0 </h2>
- <p class="jc-default">Our goal here is to be completely dependent on
- the component interface and provide extensive data object extensions
- by this point in time. </p>
- <ul>
- <li class="jc-default"> <b>Aynchronous DataObjects</b><BR>
- We need to have the ability to have DataObjects that are capable
- of asynchronous updates/adds. This will only exist in a non-transacted
- environment. </li>
- <li class="jc-default"><strong>Active Cache<br>
- </strong>Our goal here is to have the Cache system be smart enough
- and flexible enough to asynchronously grab objects and register
- for updates to the cache. </li>
- <li class="jc-default"><strong>Conflict Manager<br>
- </strong>The system should have a built in conflict manager to
- help resolve concurrency issues. </li>
- <li><span class="jc-default"><strong>JSF Compatibility Tested </strong></span></li>
- </ul>
- </TD>
- </TR>
- </TBODY>
- </TABLE>
-</DIV>
-<P><FONT color="#666666" size="2" face="Arial, Helvetica, Verdana">Copyright © 2002-2004 <A href="http://www.jcorporate.com" target="_blank">Jcorporate
- Ltd</A>. All rights reserved. <A href="http://www.jcorporate.com/html/aboutus/copyright.htm">Copyright</A> <A href="http://www.jcorporate.com/html/aboutus/privacy.htm">Privacy</A> <A href="http://www.jcorporate.com/html/aboutus/privacy.htm"><BR>
- </A></FONT><FONT face="Arial, Helvetica, Verdana" color="#666666" size="1"><BR>
- Last Modified:
- <!-- #BeginDate format:En2 -->24-Apr-2004<!-- #EndDate -->
-</FONT></P>
+<BODY vlink="#0000FF" alink="#000000" bgcolor="#FFFFFF" text="#000000" link="#0000FF" class="jc-default">
+<h1 align="center">Expresso Road Map<A name="Top"></A></h1>
+<p class="jc-explanation">This document contains a high-level overview of the
+ development work currently underway in Expresso, and a list of what features
+ are expected in what release in the near future. By it's very nature, this
+ document is evolving based on the needs of the community. </p>
+<TABLE border="0" width="100%">
+ <TBODY>
+ <TR>
+ <TD valign="top">
+ <H4>Version:</H4>
+ </TD>
+ <TD valign="top">
+ <P class="jc-default">Expresso 5.6</P>
+ </TD>
+ <TD valign="top">
+ <H4>Maintainer:</H4>
+ </TD>
+ <TD valign="top">
+ <P class="jc-default"><A href="mailto:scann at jcorporate.com?Subject=Expresso prerequisites">Sandra
+ Cann</A></P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<h2>Introduction</h2>
+<P class="jc-default">This document is intended to provide an overview of planned
+ features in upcoming Expresso releases. As such the <B> below list of features
+ to be added does NOT take into account many contributions from community developers.</B> Open
+ source is driven by the needs of the community and hence developers will contribute
+ additional features based on what they needed for their own development. The
+ benfit of contributing is the developer stays with release product and their
+ contributions are then enhancemend and improved upon by the community brainshare.<BR>
+ <BR>
+ We'd like to encourage contributors to document their code changes as part
+ of the contribution. Also think about J2EE design patterns and aim to create
+ a more flexible framework, specifically more decoupling between its parts and
+ creating documentation to faciliate understand functionality and Expresso's
+ design patterns. If/when possible we'd also like to see UML diagrams about
+ various aspects of the framework, as well as a "large view" collaboration
+ diagram for the components that make up the overall architectural framework.
+<P class="jc-default">Please also see:
+<OL>
+ <LI class="jc-default"><A href="http://www.jcorporate.com/html/customers/developers/releasemgmt.html" target="_blank">Release
+ Management</A> document.
+ <LI class="jc-default">"<A href="http://www.jcorporate.com/expresso/components/internal/tasks.jsp?project=EXPRESSO" target="_blank">Task
+ List</A>" for an up-to-date listing of the current development tasks
+ and team member assignment.
+ <LI class="jc-default">If you'd like to volunteer for one of the below tasks
+ or have a contribution to add to a release please let us know at <A href="mailto:support at jcorporate.com?Subject=Would like to work on item in task list">support at jcorporate.com</A>.
+</OL>
+<HR>
+<h2>Expresso 5.X releases</h2>
+<h3>Release 5.5 [Last stable release]</h3>
+<p class='jc-default'>Release 5.5 started towards the goal of a basic service-oriented
+ architecture, much in the way that JBoss has a microkernel architecture surrounded
+ by MBean services and included the Struts 1.1 integration and many other improvements. </p>
+<UL>
+ <li class="jc-default" style='color:red'>A critical security fix has been recently
+ addressed that allowed SQL injection attacks!
+</UL>
+<p class="jc-default">No new Bug Fixes will be applied to this release as it
+ is no longer the current stable release.</p>
+<HR>
+<h3>Release 5.6 [Current stable release]</h3>
+<p class='jc-default'>Release 5.6 focuses on additional open source packages
+ integration. There will be no addition 5.6.x releases unless a critical bug
+ is found.</p>
+<p>5.6.x Releases</p>
+<ul>
+ <li>If a bug is considered critical, then it will go into the 5.6 code base
+ immediately even if it could be potentially higher risk as to causing regression
+ errors. </li>
+ <li>Any other bugs that are 'high risk' or require a significant structural
+ change that aren't critical will go into the 5.7 code base. </li>
+ <li>NO Schema Changes, no new features and no minor bugs in 5.6.x releases. </li>
+</ul>
+<HR>
+<h3>Release 5.7 [Code presently in CVS]</h3>
+<p class="jc-default">Release 5.7 is focusing on :</p>
+<ul>
+ <li>Completing the Struts 1.2.6 Integration which underway in cvs.</li>
+ <li>Code Review of numerous contributions which are in cvs. </li>
+ <li>Integrating more of the doc into the EDG and adding sections like a book
+ format</li>
+</ul>
+<p class="jc-default">The intention is to come out with another release within
+ a couple of weeks of 5.6.
+<HR>
+<h3>Release 5.8 </h3>
+<p class="jc-default">Release 5.8 will focus on :</p>
+<ul>
+ <li>JSF Integration</li>
+ <li>Code Review of community contributions committed to cvs. </li>
+</ul>
+<HR>
+<br>
+<h3>Release 5.9 - 5.x direction</h3>
+<p class="jc-default">If there are other 5.x releases after 5.8, the basic direction
+ of 5.X is to continue to include any changes that can be added in without drastically
+ changing the available API. Programmers should only require minor changes to
+ update from one version to another. </p>
+<ul>
+ <li class="jc-default">After 5.8 the intention is to focus on the component
+ manager and service-oriented architecture, much in the way that JBoss has
+ a microkernel architecture surrounded by MBean services.</li>
+ <li>Largely backwards compatible feature additions. (a current example of this
+ is the SSL->NonSSL->SSL transition framework that was added) </li>
+</ul>
+<HR>
+<h2>Release 6.0 </h2>
+<p class="jc-default">Our goal here is to have completed:</p>
+<ul>
+ <li class="jc-default"><strong>Service-oriented Architecture</strong>: much
+ in the way that JBoss has a microkernel architecture surrounded by MBean
+ services.</li>
+ <li class="jc-default"><B>Component Manager</B>: Expresso needs the ability
+ to 'deploy' components into the appropriate location. So you can install
+ and uninstall components at will into your development environment. The component
+ manager is already in 5.X series and goal here is to have completed a stable
+ component interface and provide extensive data object extensions by this
+ point in time</li>
+</ul>
+<h3>Release 6.X</h3>
+<p class="jc-default">Our goal here is to:</p>
+<ul>
+ <li class="jc-default"> Convert each API or component area into service-oriented
+ architecture (like JMX). </li>
+ <li><b>Aynchronous DataObjects</b>: We need to have the ability to have DataObjects
+ that are capable of asynchronous updates/adds. This will only exist in a
+ non-transacted environment.</li>
+ <li><strong>Active Cache</strong>: Our goal here is to have the Cache system
+ be smart enough and flexible enough to asynchronously grab objects and register
+ for updates to the cache.</li>
+ <li><strong>Conflict Manager</strong>: The system should have a built in conflict
+ manager to help resolve concurrency issues. </li>
+</ul>
+<h2>Task List for Releases</h2>
+<p class="jc-default">In addition to the items mentioned we encourage community
+ members to contribute other code contributions. Some current ideas on the Expresso
+ community development wish list include the following. These are just a few
+ ideas for example stake. In the open source world, many people come up with
+ many fantastic ideas that can work well in the current framework. Our goal
+ is to have updated security interfaces to allow for better integration into
+ other J2EE Environments. </p>
+<ul>
+ <li>Allow each schema to define it's own valid values for the setup table.
+ Thus many items on the setup table could simply be drop down boxes. </li>
+ <li><strong>Complete Pluggable look and feel:</strong> Stylesheets should be
+ at least switchable through the setup table, and perhaps if the webadmin
+ wishes to allow it, switchable through the user preferences. </li>
+ <li> <strong>Ttiles Layouts</strong>: Get rid of frame.jsp and replace it with
+ tiles layouts. </li>
+ <li><b>Updated DBMaint User Interface</b>: Our goal here is to prototype and
+ publish and updated and new modern look to DBMaint.</li>
+ <li><b>Create DAO Query Object</b>: Data objects need to have the QueryObject
+ fully implemented for JDBC.</li>
+ <li><b>Continued Componentization:</b> Continue to componentize other systems
+ in Expresso as time allows.</li>
+ <li><b>JAAS Integration</b>: checkLogin() and Login needs to be fully integrated
+ with JAAS so that we can better support integration with Application services.</li>
+ <li><b>Security Manager Factory</b>: com.jcorporate.expresso.core.security.SecurityManagerFactory
+ needs to be implemented that will construct the appropriate permissions for
+ each system. We also need a security manager to help centralize security
+ checks.</li>
+ <li><b>UserRole Interface</b>: UserGroups needs to be abstracted into an interface</li>
+ <li><b>Native DataField Types</b>: We need DefaultDataField to be able to support
+ natively multiple data types. For example, we need it to be able to support
+ Dates natively while converting back and forth so we can reduce CPU time. </li>
+</ul>
+<P class="jc-default"> </P>
+<P class="jc-default">Copyright © 2001-2005 Jcorporate Ltd. All rights reserved. <A href="http://www.jcorporate.com/html/aboutus/copyright.htm">Copyright</A> <A href="http://www.jcorporate.com/html/aboutus/privacy.htm">Privacy</A></P>
+<h5 align="left"><FONT face="Arial, Helvetica, Verdana" color="#666666" size="1">Last
+ Updated:
+ <!-- #BeginDate format:En2 -->23-Jan-2005<!-- #EndDate -->
+ </FONT></h5>
+<P> </P>
</BODY>
</HTML>
More information about the cvs
mailing list