OpenCms 6.0 alpha 3 released
Alkacon Software has finished work on the third public binary alpha release of OpenCms 6.0. OpenCms 6.0 is a major upgrade, and it vastly expands the features of OpenCms 5.0.
This alpha 3 release improves the features of the new XML content and adds support for Java 1.5
When will the "final" release of OpenCms 6.0 be available?
We now do expect the final release of OpenCms 6.0 end of Q1 2005. You can help speeding up the process of development by providing feedback for this release and the following releases, especially regarding bugs. In case you find any bug, please use the OpenCms bugzilla to document it. The more feedback and code contributions are made, the faster we can fix the issues and finish the development.
The most important new features in this alpha 3 release compared to the alpha 2 version:
- Support for Java 5.0 / 1.5 and PostgreSQL:
- Fixed issue with setup wizard in JDK 5.0
- OpenCms now installs and runs with JDK 5.0 (please note: no exhaustive tests have been done so far)
- Added support for the PostgreSQL database (thanks to Antonio Core for his contribution)
- Optimized DB queries and index generation for MySQL
- Improved DB performance on MySQL after heavy testing
- JSP based re-implementation of the "Galleries" with new features:
- Added new "Image gallery" dialog for WYSIWYG editor (also available as XML content widget)
- Added new "Download gallery" dialog for WYSIWYG editor (also available as XML content widget)
- Added new "External link gallery" dialog for WYSIWYG editor (also available as XML content widget)
- Added new "HTML gallery" dialog for WYSIWYG editor (also available as XML content widget)
- All galleries are now available for the (optional) HTMLArea editor
- Modified VFS to allow multiple folder resource types
- Added new resource types for image, download, link and html galleries
- Resource "type change" dialog can now also change the type of a folder (e.g. to a gallery type)
- XML content improvements and new features:
- Added XML content handler interface for special action in the XML content lifecycle
- Added full text search capabilities for XML content data
- Default implementation of XML content handler is org.opencms.xml.content.CmsDefaultXmlContentHandler
- XML content now allows variable mapping of XML content widgets to schema types
- XML content editor can now handle optional elements (min occurs = 0) from the XML schema
- XML content editor can now handle multiple elements (max occurs > 1) from the XML schema
- XML content now allows validation and error handling in editor with customizable validation rules
- Widgets for XML contents can now be configured independent from schema types
- Removed "index" attribute from "contentshow" tag (use "element=name") to directly access an element index value > 0
- Added support for nesting XML content definitions
- Added internal caching for XML content definitions
- Further improvements:
- Source code for the 'templateone' default module is now available in the src-modules CVS subfolder
- VFS resource types and Workplace context menus can now be added by a module
- Configuration of default VFS files (e.g. index.html) has been moved to opencms-vfs.xml
- Added GUI to modify property values and delete definitions in Administration view
- Property definitions can be deleted from Admin GUI even if resources still use the property
- Added support for language - country based locales in the Workplace
- Updated Lucene to latest stable version 1.4.3, plus an additional patch to prevent NPE in the Lucene index manager
- Resolved Issues:
- Fixed issue with deleted users or groups causing "orphan" ACE entries (causing NPE errors in the Workplace permission dialog)
- Fixed issue with upload applet not working in root site "/"
- Fixed issue with HTML comments in editor causing invalid HTML documents
- Fixed issue with shutDown() method of modules not being called
- Fixed issue with Lucene search engine not correctly indexing pages based on non-ISO encoding
- Fixed issue with password change being broken in the user administration
- Fixed issue with "https" scheme not correctly working in site configuration
For a list of features of the 6.0 release compared to the 5.0 release, please check the news archive for the release note of the 6.0 alpha 1 version.
Who should use this 6.0 alpha 3 version?
This is an alpha version. Please don't expect it to be perfectly stable. One of the most important Open Source philosophies is "Release early, Release often", and this is what we intend to do with this and subsequent 6.0 releases. If and how you should use this version depends on what your goals are:
- If you are currently using any previous 6.0 development release (e.g. 6.0 alpha 1 or alpha 2), you should upgrade to this new version.
- If you are an IT professional or a company working with OpenCms on a regular basis, you should definitely check if and how your current websites, modules and functions can be ported to the new release. Even though changes on the Java API level and changes on the DB schema are to be expected until we reach the beta or even release candidate state of the development, most of the big changes have already been made.
- If you start a new project that is expected to go live in about 3 months, you may use this version to build your project - but be prepared for some extra work to update when new releases become available, and also for some time figuring out the so far undocumented features if these are required.
- If you are working on a project with OpenCms 5.0.x that has a delivery date soon, you should stick to the 5.0.x version unless you absolutely require a feature of the 6.0 version.
- If you are running a website based on OpenCms, and you plan to implement some new features in the not so far future, you should install this version on a test machine and check out the new features.
TODO list to be finished before OpenCms 6.0 is released:
- The OpenCms workplace is still not fully implemented in JSP - all XmlTemplate using dialogs will be rewritten to JSP
- More of the configuration will be transferred from opencms.properties to the new Digester XML based configuration file, the current opencms.properties will stay only for the database configuration - this configuration will be moved to the XML in a release after 6.0.
- The most important management functions (e.g. cache maintainance, system status) will be exposed to allow JMX containers to manage OpenCms
- Documentation needs to be revised for old functions and written for new functions
- Testing and bug fixing - your feedback is required!
- The development of the Content Releationship Engine (CRE) initially scheduled for the 6.0 release has been moved to a version past the 6.0 release.
The team at Alkacon Software - The OpenCms Experts wants to thank everyone who has contributed to this release of OpenCms.