www.pudn.com > jsptree-1.0-b6-src.zip > HISTORY
JSP Tree v1.0-b6
======================================
http://jsptree.sourceforge.net/
This document describes the history of the JSP Tree project by listing the
changes made for each release.
Release: 1.0-b1, 2002-Dec-20
============================
* Initial release.
Release: 1.0-b2, 2003-March-17
============================
* Log4J integration
* Ability to specify user's node renderer(skin) without hacking in source code
* Support of XML tree factory
* Servlet example was added
* Added example of how to specify http link for tree node
* Tree Factory retrofitted in order to support multiple tree instances
* Code Refactoring: Interface TreeFactory changed; Interface SkinFactory introduced; Interface JSPTreeNode changed;
* A few bugs were fixed
Release: 1.0-b3, 2003-May-20
============================
* Ability to specify opened nodes for XML tree.
* Bug: XML tree factory created shared instance of Tree instances. Fixed.
* Introduced html templates for tree's nodes, in order to avoid keeping html code in java classes (renderers)
* Ability to use JSP Tree with Struts & Tiles.
* Extended example web application
Release: 1.0-b4, 2003-Jul-23
============================
* Refactoring Skin interface. NodeInfo is introduced.
* MenuTemplateSkin is not thread safe. Fixed.
* All generated URL should be encoded with HttpResponse.encodeRedirectURL()
* In all URLs the sign "&" is replaced to "&"
* package net.sf.jsptree.tree is refactored completely
* JavaDoc
Release: 1.0-b5, 2004-Jul-5
============================
* Fixed DefaultTreeNode#clone() method that mistakenly copied new generated child nodes into old one.
It caused a serious bug when nodes' states were shared between multiple sessions.
* An arbitrary order of jsp tag's attributes caused a NullPointerExceptions. Fixed.
Release: 1.0-b6, 2005-Jan-30
============================
* Tree's structure and its current state(opened and selected nodes) are completely decoupled.
It is possible now to share tree structure between multiple concurrent sessions without having to
share actual tree state (different users see different opened and selected nodes). It helps to
alleviate the memory problem in case of big data structures.
* Added an ability to set up a custom Comparator; it helps to sort child nodes in the correspondence
with a desired strategy.
* Added an ability to reference custom values being specified in the xml data without writing
a custom renderer(skin).