Tagger Cat Read me

The Tagger Cat read me and change summary

TaggerCat Version=2.1 Build=20090309_1009

Change List #60

===========================================================
Summary of Changes
===========================================================

• Enhancements:

Added a User Setting Class and associated Tags and Handler.

A User Setting class has been added, with an associated Tag, and action Handler. The User Settings class is used to maintain an arbitrary map of user specific settings; similar to what would have been done with client side cookies.

Changed the way the entity resolver checks for duplicate Entities on the session.

The check for duplicate entity entries on the session has changed, and writes a warning event to the log.

Changed the Tagger Cat standard JS code.

The taggercat JS code has been cleaned up, and is a bit more Object Oriented ( less polluting of the global address space).

TaggerCat Version=2.1 Build=20080917_0842

Change List #47

===========================================================
Summary of Changes
===========================================================

• Enhancements:

RESTful URLs are now supported.

Restful URLs are now fully supported. Like almost everything else in the framework, the RESTful URL functionality leverages the system metadata.

The Restful URLs automatically include entity primary keys, as well as filter criteria. See the Developer's Guide for more details.

Change List #39

===========================================================
Summary of Changes
===========================================================

• Enhancements:

The Declarative Constraint, Derivation, and ECA rules now fully support Rhino's JavaScript as a scripting language.

In previous releases, the Declarative Constraint, Derivation, and ECA (event-condition-action) rules supported only EL expressions. Now, with Rhino JavaScript you have far more capabilities with a full programming language.

The default Entity and Property administration pages now include an action button to test entered EL and Rhino JavaScript code blocks interactively.

User Time zone support.

User time zone support has been improved. User's can sets their preferred time zone and view and edit dates in their local time zone. Of course all date time values are save to the database in a consistent server time zone.

A new JSP tag named clientScope has been added.

The clientScope tag has been added to tag library. This tag is use to place an object into client scope by serializing it out to the
page in a hidden form element. When a form with the serialized object is submitted, the objects will automatically be recreated on the current request scope.
This tag is primarily intended to be used to maintain object state via the browser's page rather than on session scope.

Change List #26

===========================================================
Summary of Changes
===========================================================

• Enhancements:

The WebContext instance is now required

A WebContext object is now required, and is created with each request cycle. The Hibernate sessions are now maintained in the WebContext instance. The WebContext instance also contains a reference to the servletContext, as well as the name of the default controller servlet.

The Default Controller Servlet

The name of the default controller servlet is now specified in the applications deployment descriptor.

Deprivation rules are re-applied when rows are duplicated with the Duplicate action.

The datasource tag ( and class ) now support Cacheable and CacheRegion properties.

The chachable and cacheRegion attributes can be used to set the corresponding properties on the datasource Hibernate Criteria object.

An AfterDelete event type has been added to the DataSourceEvent type.

Added a truncate attribute to the DataFieldValueTag.

When displaying potentially long string values you can use the truncate attribute to set the max number of characters to be displayed.

TaggerCat Version=2.1 Build=20070916_1207

Change List #26

===========================================================
Summary of Changes
===========================================================

• Enhancements:

Added a WebContext class.

A WebContext object can now be created in the TaggerCatFilter, and attached to the current thread. The WebContext object contains the current HttpRequest, HttpResponse and the ServletContext objects. You can access the WebContext from anywhere in your code, such as from within ECA methods.

To include the creation of the WebContext; add the createWebContext init param as shown here:

 
	<filter>
		<filter-name>TaggerCatFilter</filter-name>
		<filter-class>com.taggercat.filter.TaggerCatFilter</filter-class>
		<init-param>
		<param-name>durationThreshold</param-name>
		<param-value>40</param-value>
		</init-param>
		<init-param>
		<param-name>hbn8Statistics</param-name>
		<param-value>true</param-value>
		</init-param>
		<init-param>
		<param-name>createWebContext</param-name>
		<param-value>true</param-value>
		</init-param>
	</filter>

Added a StatusMessage class and a StatusMessages.tag file

The StatusMessage is used to set general status messages; that are not error or exception related. See the StatusMessages.tag file for more details. The message can be displayed with the StatusMessages.tag or the technique of your choice.

Datasources build a list of deleted entities.

The dataSource class now builds a list of deleted entities during a delete operation. The list is available during a After Delete event method from an event Listener.

I18n support has been added to the DatafieldCaptionTag

The DataFieldCaptionTag now supports internationalization.

Added utility functions to the Text Class for generating Random Strings

The getRandomString( int size) has been added; we use it for generating temporary passwords.

• Bug FIxes:

XHTML support added to the DataSourceActionTag

The DataSourceAction tag now correctly generates XHTML formatted tags.

• Known Bugs :

Aggregate EL functions

A bug exists in the the derivations when aggregate functions were applied to child data sources. This bug caused the derivations to incorrectly calculate when multiple parent entities where updated in a single request.