Apache Wookie Release Notes
===========================
See https://issues.apache.org/jira/browse/WOOKIE-* (where * is the number of the issue below)

For more detailed information on significant changes, see NEW_AND_NOTEWORTHY

Version 0.9.2
=============

Bugs Fixed
===========

	* WOOKIE-184 - Tutorial for geoLocation
	* WOOKIE-239 - Files left on server when delete from a widget
	* WOOKIE-245 - Update W3C Access (WARP) tests
	* WOOKIE-246 - Licence boilerplate in JQueryMobile template widgets is incorrect 
	* WOOKIE-272 - ant run takes a long time and -Doffline=true fail
	* WOOKIE-273 - Duplicate entries in widgetrequest access policies
	* WOOKIE-280 - WebMenuServlet needlessly created widget instances
	* WOOKIE-286 - REST API mixes up Content-Type and Accept headers when choosing resource representation
	* WOOKIE-300 - Full whitelist access granted to any widget built from a template
	* WOOKIE-302 - Too many open files by Wookie
	* WOOKIE-304 - New template build file assumes wookie project is in a folder called "wookie"
	* WOOKIE-305 - Policies allow you to define the same policy twice - once with ALLOW and once with DENY
	* WOOKIE-306 - Widget Interface: Conflicts when using Clear() and SetItem()
	* WOOKIE-309 - Proxy policy of "* * DENY" is treated as ALLOW 
	
Improvements
============

	* WOOKIE-131 - Skinnable widgets
	* WOOKIE-140 - Example widget - Flickr photos API   
	* WOOKIE-141 - YouTube video API
	* WOOKIE-251 - Proxy is losing headers
	* WOOKIE-255 - Change file names to not include version numbers in features
	* WOOKIE-260 - W3C Widget conformance: Add call to icon sniifer routine into IconEntity
	* WOOKIE-281 - Use instance queues by default
	* WOOKIE-284 - Unable to run two instances of wookie on one machine
	* WOOKIE-288 - Allow WAR release artifacts to use an embedded database
	* WOOKIE-291 - Patch to tidy up Browse widget template layout at small screen size
	* WOOKIE-293 - Update log4j, slf4j and Shindig to latest versions
	* WOOKIE-295 - Test widgets from templates
	* WOOKIE-297 - Replace XSL processing in templates 
	 
New Features
============

	* WOOKIE-100 - Open ID/OAuth Support
	* WOOKIE-189 - Packaging of Wookie to run portably from a usb stick
	* WOOKIE-253 - New sample widget - Walkthrough
	* WOOKIE-276 - Better management of CSS in templating system
	* WOOKIE-277 - Better handling of template/widget provided Javascript
	* WOOKIE-299 - Create a widget browser from the browse template
	    
Known Issues
============	

	* WOOKIE-222 - There is a known issue when using Tomcat 7.* with Wookie. Sometimes when a widget is actually 
	loaded, a browser alert box sometimes appears informing the user of a "Session Error". 
					 
    This is caused by the DWR library used by Wookie for Comet-based widgets handling HTTP-only cookies incorrectly; 
    Tomcat 7 uses HTTP-only cookies as the default setting to prevent cross-site scripting (XSS) attacks.
					 
    A workaround is to add the following to the WEB-INF/web.xml file
					 
    <init-param>
        <param-name>crossDomainSessionSecurity</param-name>
        <param-value>false</param-value>
    </init-param>
					
    Note that XSS prevention will still be in place in Tomcat 7; this just disables the additional mechanism
    implemented in DWR that conflicts with it.
 
    This is an issue for DWR 2.* with Tomcat 7.* (or earlier versions of Tomcat where useHttpOnly="true" is set.)