Hi Ron, Well, it is a ground-up re-write so that in it's itself may remedy existing issues.
If you want me to be more specific, give me some current examples issues that come to mind for you. Some things that have changed (for the better IMOHO): - No longer bound to Turbine (or any other framework for that matter) - No longer uses Torque, currently J2 uses a persistence plugin for all RDBMS operation. The default plugin uses OJB. - Jetspeed 2 should be much smaller than J1 as it will have less dependencies. - Standardized the build process using Maven. - We will be using a as of yet unnamed IoC/component/JMX based framework to help make the core of J2 highly pluggable and easily configurable. - All requests go through an easily configurable pipeline, allowing users to develop there own custom valves that can work with portlet requests as they see fit. Regards, *================================* | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | *================================* > -----Original Message----- > From: Cordell, Ronald L. [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 22, 2003 12:55 PM > To: 'Jetspeed Users List' > Subject: JetSpeed 2 Development list > > Is there a list or web page that lists the key differences between > JetSpeed > 1.4 and JetSpeed 2? For example, I realize that the main goal of JetSpeed > 2 > is to incorporate the JSR168. However, I was wondering if there were other > things addressed in the 2.0 release. > > Thanks, > > Ron Cordell
