Author: psharples
Date: Tue Apr 5 15:45:34 2011
New Revision: 1089087
URL: http://svn.apache.org/viewvc?rev=1089087&view=rev
Log:
Updated release notes, readme ,building, keys files etc in advance of new build
of this branch
Added:
incubator/wookie/branches/0.9.x/BUILDING
incubator/wookie/branches/0.9.x/KEYS
incubator/wookie/branches/0.9.x/README
- copied, changed from r1087636,
incubator/wookie/branches/0.9.x/readme.txt
incubator/wookie/branches/0.9.x/RELEASE_NOTES
incubator/wookie/branches/0.9.x/etc/release/war/WAR_BUILD_NOTES
- copied, changed from r1087636,
incubator/wookie/branches/0.9.x/etc/release/war/README
Removed:
incubator/wookie/branches/0.9.x/etc/release/war/README
incubator/wookie/branches/0.9.x/readme.txt
Added: incubator/wookie/branches/0.9.x/BUILDING
URL:
http://svn.apache.org/viewvc/incubator/wookie/branches/0.9.x/BUILDING?rev=1089087&view=auto
==============================================================================
--- incubator/wookie/branches/0.9.x/BUILDING (added)
+++ incubator/wookie/branches/0.9.x/BUILDING Tue Apr 5 15:45:34 2011
@@ -0,0 +1,43 @@
+Apache Wookie - source distribution instructions
+=================================================
+
+Initial Setup
+-------------
+
+1) Install a JDK (1.6.* or higher)
+ See http://www.oracle.com/technetwork/java/javase/downloads/index.html
+ or http://java.com/en/download/
+ (Be sure to choose a JDK and not a JRE version)
+
+2) Make sure that your PATH includes %JAVA_HOME%\bin (windows) or
+ $JAVA_HOME$/bin (unix). Optionally, you may also wish to add an environment
variable
+ named %JAVA_HOME% and point that to the %JAVA_HOME%\bin folder of the java
JDK install.
+
+3) Install Apache Ant
+ See http://archive.apache.org/dist/ant/binaries/
+ for an applicable binary. Once installed ensure your PATH includes
%ANT_HOME%\bin (windows)
+ or $ANT_HOME$/bin (unix). (otherwise you won't be able to run it unless
you are in the
+ %ANT_HOME%\bin folder.) NOTE: There is a known issue when using Ant
version 1.8.x to build and run
+ Wookie; you should instead use version 1.7.1. To check which version of
ant you are using, type
+ ant -version. See the RELEASE_NOTES for more information.
+
+4) Build using default ant target (Optional - skip to 5 if you want to compile
& run together)
+ Navigate to the top level of the source distribution in a command
prompt/console window.
+ Type "ant", to start the build process. The first time you run this
command all dependencies will
+ be downloaded so you must be online and it will take some time.
Subsequent builds will be much faster.
+
+5) Run Wookie
+ The quickest way to run Wookie is in "standalone" mode; in this mode
Wookie uses a local database and
+ embedded server. This is a good way to experiment with Wookie in
development. Navigate to the root folder
+ of the source distribution in a command prompt/console window. Once
there type "ant run".
+
+ Once the server is running go to 'http://localhost:8080/wookie' in your
favourite browser.
+
+6) Additional Information
+ Note that by default, Wookie will clean the database each time it is
run, this ensures that your development
+ environment starts in a consistent state. However, any modifications
you have made to the database during
+ previous runs will be lost. To run the development server without
cleaning the database you need to set initDB=false.
+
+ To access the administration menu (http://localhost:8080/wookie/admin)
use the username 'java' and password 'java'.
+
+ If you want to start with a completely clean build then use "ant
clean-build run" at the console/command prompt.
\ No newline at end of file
Added: incubator/wookie/branches/0.9.x/KEYS
URL:
http://svn.apache.org/viewvc/incubator/wookie/branches/0.9.x/KEYS?rev=1089087&view=auto
==============================================================================
--- incubator/wookie/branches/0.9.x/KEYS (added)
+++ incubator/wookie/branches/0.9.x/KEYS Tue Apr 5 15:45:34 2011
@@ -0,0 +1,23 @@
+This file contains the PGP and GPG keys of Apache Wookie
+developers. Please don't use them for email unless you have
+to. Their main purpose is code signing.
+
+Users: pgp < KEYS
+ gpg --import KEYS
+
+Wookie Developers:
+ pgp -kxa <your name> and append it to this file.
+ (pgpk -ll <your name> && pgpk -xa <your name>) >> this file.
+ (gpg --list-sigs <your name> \
+ && gpg --armor --export <your name>) >> this file.
+
+************************************ PLEASE NOTE
**********************************************************
+
+ Edit this file in SVN at
+ https://svn.apache.org/repos/asf/incubator/wookie/trunk/KEYS
+
+ N.B. use a command such as the following to check it out without
downloading every Wookie module:
+ svn co --depth=files
https://svn.apache.org/repos/asf/incubator/wookie/trunk/
+
+************************************************************************************************************
+// TODO - finish this off!
\ No newline at end of file
Copied: incubator/wookie/branches/0.9.x/README (from r1087636,
incubator/wookie/branches/0.9.x/readme.txt)
URL:
http://svn.apache.org/viewvc/incubator/wookie/branches/0.9.x/README?p2=incubator/wookie/branches/0.9.x/README&p1=incubator/wookie/branches/0.9.x/readme.txt&r1=1087636&r2=1089087&rev=1089087&view=diff
==============================================================================
--- incubator/wookie/branches/0.9.x/readme.txt (original)
+++ incubator/wookie/branches/0.9.x/README Tue Apr 5 15:45:34 2011
@@ -1,260 +1,68 @@
-Wookie
-======
-Welcome to Wookie!
+Welcome to Apache Wookie
+=========================
+Apache Wookie is a Java server application that allows you to upload and
deploy
+widgets for your applications; widgets can not only include all the usual
kinds
+of mini-applications, badges, and gadgets, but also fully-collaborative
applications
+such as chats, quizzes, and games.
+
+Wookie is based on the W3C Widgets specification, but widgets can also be
included
+that use extended APIs such as Google Wave Gadgets and OpenSocial.
+
+Administrators can upload Widgets packaged according to the W3C Widgets
specification,
+and makes these available to applications using a REST API. Applications
typically have
+a plugin that implements this REST API, and enables users to pick widgets from
a gallery
+of those available to add to their pages.
+
+There is a Connector Framework included in Wookie for many different
programming
+languages that simplifies the process of writing plugins.
-Apache Wookie is a Java server application that allows you to upload and
deploy widgets for your applications; widgets can not only include all the
usual kinds of mini-applications, badges, and gadgets, but also
fully-collaborative applications such as chats, quizzes, and games.
-
-Wookie is based on the W3C Widgets specification, but widgets can also be
included that use extended APIs such as Google Wave Gadgets and OpenSocial.
-
-Apache Wookie is an effort undergoing incubation at The Apache Software
Foundation (ASF). Incubation is required of all newly accepted projects until a
further review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project has
yet to be fully endorsed by the ASF.
-
-Administrators can upload Widgets packaged according to the W3C Widgets
specification, and makes these available to applications using a REST API.
Applications typically have a plugin that implements this REST API, and enables
users to pick widgets from a gallery of those available to add to their pages.
There is a Connector Framework included in Wookie for many different
programming languages that simplifies the process of writing plugins.
-
-For more information see http://incubator.apache.org/projects/wookie.html
-
-Questions? Need Help?
+Incubation Disclaimer
=====================
-If you have questions about Wookie, please check the FAQ (see
http://incubator.apache.org/wookie/faq.html) to see if someone has already
posted an answer to your question. Failing that, you can post a message to
either the wookie-dev or wookie-user mailing list; to subscribe to a mailing
list, send an email with the subject "subscribe" to
"[email protected]" or
"[email protected]"
-
-Downloading & Building Wookie
-=============================
-
-Running Wookie in "standalone" mode
-===================================
-The quickest way to run Wookie is in "standalone" mode; in this mode Wookie
uses a local database and embedded server. This is a good way to experiment
with Wookie in development.
-
-To run Wookie in standalone mode:
-
-> cd PROJECT_HOME_DIRECTORY
-> ant run
-
-The first time you run wookie (or compile it) any required libraries will be
downloaded, this can take some time and requires a network connection.
+Apache Wookie is an effort undergoing incubation at the Apache Software
+Foundation (ASF), sponsored by the Apache Incubator PMC.
-Note that by default, wookie will clean the database each time it is run, this
ensures that your development environment starts in a consistent state.
However, any modifications you have made to the database during previous runs
will be lost.
+Incubation is required of all newly accepted projects until a further review
+indicates that the infrastructure, communications, and decision making process
+have stabilized in a manner consistent with other successful ASF projects.
+
+While incubation status is not necessarily a reflection of the completeness or
+stability of the code, it does indicate that the project has yet to be fully
+endorsed by the ASF.
-To run the development server without cleaning the database you need to set
initDB=false. See the next section for more details.
-
-Once the server is running go to http://localhost:8080/wookie
-
-To access the administration menu (http://localhost:8080/wookie/admin) use the
username 'java' and password 'java'.
-
-If you want to start with a completely clean build then use:
-
-> cd PROJECT_HOME_DIRECTORY
-> ant clean-build run
-
-Running options
+Getting Started
===============
-To set run mode options you can either add properties to the
local.build.properties file or you can pass properties in via the command line
using -Drun.args="<property_name>=<property_value>
<property_name>=<property_value>". For example:
-
--Drun.args="port=8080 initDB=false"
-
-Available properties are:
-
-Property | Values | Description
| Default
-------------------------------------------------------------------------------------
-initDB | True or False | Initialise the DB to a default
configuration| True
-port | Integer | Set the port on which the server is to run
| 8888
-
-Running Wookie in debug mode
-=============================
-You can start Wookie in debug mode using JDSPA with the following command:
-
-> ant -Djvmargs="-Xdebug
-Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=n" clean-db run
-
-Once Wookie is running in debug mode you need to connect to it using your
debugger.
-
-Debugging with Eclipse
-======================
-To connect Eclipse to Wookie running in debug mode on your local machine you
would:
-
-> Run -> Debug Configurations...
-
-> Select "Remote Java Application"
-
-> Click "New Launch Configuration"
-
-Set as follows:
-
-Name: Wookie Debug (Localhost)
-Project: Click "Browse" and select your Wookie project
-PORT: 8001
-
-Now click the "Debug" button (note you must be running Wookie in debug mode,
see above, first).
-
-You can now set breakpoints etc. as if you were running from within Eclipse.
-
-Once you have set up this "debug configuration" you can quickly access it from
your debug menu.
-
-For more on remote debugging with Eclipse see
http://www.eclipsezone.com/eclipse/forums/t53459.html
-
-Note, you can set up a run configuration to be able to run Wookie from the UI
of Eclipse, but I'll leave that for you to work out as I use the command line.
-
-Running Wookie with Tomcat and MySQL
-====================================
-The following will compile and run the server in Tomcat with a specified RDBMS
using JPA persistence. The database schema can be defined and populated on
launch, however you must have previously done the following:
-
-1. Obtained a JDBC driver jar file for the database,
-2. created an empty database for Wookie's persistent storage, and
-3. have valid database credentials to access it.
-
-Make the following changes to configure build.properties, (substituting
CATALINA_HOME with the absolute or relative path to Tomcat's installation
directory and specifying the database driver, url, type and credentials
connection information):
-
-widget.deploy.dir=CATALINA_HOME/webapps/wookie/deploy
-servletEngine.webapp.dir=CATALINA_HOME/webapps
-servletEngine.container.lib.dir=CATALINA_HOME/lib
-servletEngine.context.conf.dir=CATALINA_HOME/conf/Catalina/localhost
-wookie.persistence.manager.type=jpa
-wookie.db.user=java
-wookie.db.password=java
-wookie.db.driver=com.mysql.jdbc.Driver
-wookie.db.uri=jdbc:mysql://localhost:3306/widgetdb
-wookie.db.type=mysql
-jdbc.driver.path=../mysql-connector-java-5.1.7.jar
-
-The wookie.db.type setting can accept the following values: db2, derby,
hsqldb, mssql, mysql, mysql5, oracle, oracle9, oracle10, postgresql, and
sybase. The jdbc.driver.path setting can be absolute or relative file path to
the driver jar archive.
-
-To ensure the configuration changes are propagated into the Wookie build
artifacts, perform a full clean build after changing build.properties:
-
-> cd PROJECT_HOME_DIRECTORY
-> ant clean-build deploy-webapp
-
-To force Wookie to define or reset the database schema on the first start, use
the following commands to start the Tomcat server:
+For a source distribution, please read BUILDING for
+instructions on building Apache Wookie.
-> cd PROJECT_HOME_DIRECTORY
-> export CATALINA_OPTS="-Dwidget.persistence.manager.initstore=true"
-> CATALINA_HOME/bin/startup.sh
-
-To shutdown the Wookie Tomcat server and clear the initialization flag:
-
-> cd PROJECT_HOME_DIRECTORY
-> CATALINA_HOME/bin/shutdown.sh
-> export CATALINA_OPTS=
-
-There are also SQL scripts for all of the valid database configurations built
as part of Wookie that can be used to initialize the database schema manually
if desired. These are located here:
-
-build/classes/org/apache/wookie/beans/jpa/db2-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/derby-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/hsqldb-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/mssql-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/mysql5-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/mysql-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/oracle10-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/oracle9-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/oracle-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/postgresql-wookie-schema.sql
-build/classes/org/apache/wookie/beans/jpa/sybase-wookie-schema.sql
-
-The Wookie server will populate the newly initialized database with seed data
to complete the process when started.
-
-You will need to create a user with the role "widgetadmin" in your tomcat
installation. For example, add the following to tomcat-users.xml:
-
-<role rolename="widgetadmin"/><user username="java" password="java"
roles="widgetadmin"/>
-
-If you have previously used Wookie in standalone deployment, to ensure the
right scripts are included in the build you need to run:
-
-> ant clean-build
-
-Then to build and deploy the webapp, run:
-
-> ant deploy-webapp
-
-You can then start Tomcat as usual.
-
-To access the administration menu (http://localhost:8080/wookie/admin) use the
username 'java' and password 'java'.
-
-If you want to start with a completely clean build then use:
-
-> ant clean-build deploy-webapp
-
-Running Wookie with a security manager
-======================================
-NOTE: This section was written before moving from Hibernate to OpenJPA/JCR and
so some of these instructions may no longer be correct.
-
-If you are running Wookie with a security manager you will have to grant some
permissions to get Wookie running properly. Otherwise you are likely to run
into this of a similar error:
-
-SEVERE: Exception sending context initialized event to listener instance of
- class org.apache.wookie.server.ContextListener
-java.security.AccessControlException: access denied
-(java.util.PropertyPermission user.dir read) at ...
-If you can't turn off the security manager but don't really care about it, you
can consider to replace to contents of the policy file (in Tomcat this is
typically $TOMCAT_HOME/conf/catalina.policy, Ubuntu users will find the policy
files in /etc/tomcat6/policy.d/) with the grant all statement:
-
-grant {
- permission java.security.AllPermission;
-};
-
-This is not a recommended way of working for a production environment, because
it effectively means turning off security alltogether.
-
-Another option is to properly configure the security policy file. Below is a
list of permissions that Wookie needs. Most of these are for Hibernate that
needs to generate 'enhanced' classes at runtime.
-
-// fixes access denied (java.util.PropertyPermission user.dir read)
-grant {
- permission java.util.PropertyPermission "*", "read,write";
-};
-
-// fixes access denied (java.io.FilePermission
TOMCAT_HOME\bin\local.widgetserver.properties read)
-grant {
- permission java.io.FilePermission
- "<<ALL FILES>>", "read, write";
-};
-
-// fixes access denied (java.net.SocketPermission localhost resolve)
-grant {
- permission java.net.SocketPermission "*", "resolve,connect";
-};
-
-// fixes access denied (java.lang.RuntimePermission
accessClassInPackage.org.apache.catalina)
-// fixes access denied (java.lang.RuntimePermission accessDeclaredMembers)
-// fixes access denied (java.lang.RuntimePermission getProtectionDomain)
-grant {
- permission java.lang.RuntimePermission
"accessClassInPackage.org.apache.catalina";
- permission java.lang.RuntimePermission "accessDeclaredMembers";
- permission java.lang.RuntimePermission "getProtectionDomain";
-};
-
-// fixes access denied (java.lang.reflect.ReflectPermission
suppressAccessChecks)
-grant {
- permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
-};
-
-Note that some of these fixes are still not very strict, which means that if
you
-are really concerned to limit permissions as much as possible, you need to
define
-stricter rules, but it's a start and should get your Wookie instance
up-and-running.
-
-For more information how to do this in Tomcat, see the Security Manager HOW-TO
-
-Running Wookie using embedded Jackrabbit JCR
-============================================
-The folloing property is used to switch the standalone or Tomcat deployed
servers to utilize JCR for persistence via an embedded JCR instance:
-
-wookie.persistence.manager.type=jcr
-
-Additional properties must be configured to specify the desired JCR root node
path and credentials for tomcat deployments:
-
-wookie.repository.user=java
-wookie.repository.password=java
-wookie.repository.rootpath=/wookie
-wookie.repository.workspace=default
-
-These replace the wookie.db.* and jdbc.drive.path settings above, but
otherwise the instructions apply for the JCR configuration.
-
-Running Wookie with other configurations
-========================================
-Other configurations of Wookie can also be run; the main requirements are a
servlet container and a database.
-
-Database connections can be set up using either JPA (Java Persistence API) or
JCR; the configuration details are set in build.properties. Additional
configuration for advanced use can be found in
org.apache.wookie.beans.jpa/peristence.properties. The database schema and
mappings is located in etc/ddl-schema.
-
-The deploy-webapp task can be used to deploy Wookie to any servlet container
application.
-
-Running Wookie in a virtual host configuration
-==============================================
-This has been noted as an issue with the current release (see WOOKIE-111).
-
-If anyone has any advice on resolving this issue, then please do comment on
the issue at https://issues.apache.org/jira/browse/WOOKIE-111
-
-Building and deploying widgets
-==============================
-See the instructions in widgets/readme.txt
+Apache Wookie is made available in a standalone binary distribution,
+which means that once you download it, you should be able to run wookie
+'out of the box' without having to download and configure any other components
+ * Please read STANDALONE_BUILD_NOTES for this
+
+Additionally a WAR archive binary distribution is also made available for
Wookie.
+This is designed for users who wish to use/integrate Wookie into their
existing server
+environment - an existing Tomcat instance for example.
+ * Please read WAR_BUILD_NOTES for this
+
+You may also want to refer to RELEASE_NOTES for list of supported and
unsupported
+features.
+Questions? Need Help?
+=====================
+If you have questions about Wookie, please check the FAQ
+(see http://incubator.apache.org/wookie/faq.html) to see if someone has
already
+posted an answer to your question. Failing that, you can post a message to
either the
+wookie-dev or wookie-user mailing list; to subscribe to a mailing list, send
an email
+with the subject "subscribe" to "[email protected]" or
+"[email protected]"
+
+More information on Wookie
+===========================
+We welcome contributions, and encourage you to get involved in the Wookie
+community. If you'd like to learn more about how you can contribute, please
+see: http://incubator.apache.org/wookie
+Thank you for using Wookie
+The Apache Wookie Team
+http://incubator.apache.org/wookie
\ No newline at end of file
Added: incubator/wookie/branches/0.9.x/RELEASE_NOTES
URL:
http://svn.apache.org/viewvc/incubator/wookie/branches/0.9.x/RELEASE_NOTES?rev=1089087&view=auto
==============================================================================
--- incubator/wookie/branches/0.9.x/RELEASE_NOTES (added)
+++ incubator/wookie/branches/0.9.x/RELEASE_NOTES Tue Apr 5 15:45:34 2011
@@ -0,0 +1,129 @@
+Apache Wookie Release Notes
+===========================
+See https://issues.apache.org/jira/browse/WOOKIE-* (where * is the number of
the issue below)
+
+Version 0.9.0 Released 2011-04-**
+=================================
+
+Bugs Fixed
+===========
+ * [WOOKIE-9] - Return Widget types in all Widget representations
+ * [WOOKIE-10] - Add methods to API for getting list of widgets by type
+ * [WOOKIE-37] - Make wookie to conform to W3C Widgets API
+ * [WOOKIE-92] - Add Locale parameter for requesting a widget instance
+ * [WOOKIE-94] - Add filter to enable folder-based localization
+ * [WOOKIE-95] - Update documentation on use of Locale parameters
+ * [WOOKIE-96] - Ensure all start files have JS injected
+ * [WOOKIE-97] - Recode default widgets to use W3C localization model, and
remove old localization shared JS
+ * [WOOKIE-122] - Create an admin user interface to review, grant and
revoke widget access requests
+ * [WOOKIE-13] - java.sql.SQLException: Connections could not be acquired
from the underlying database!
+ * [WOOKIE-21] - Website sync script
+ * [WOOKIE-23] - Invalid web.xml files
+ * [WOOKIE-25] - Reporting failed API request as success
+ * [WOOKIE-40] - Website Sync not working
+ * [WOOKIE-42] - Wookie rewrites HTML start file incorrectly when injecting
JavaScript, where there are self-closing script tags
+ * [WOOKIE-43] - SQL script incorrectly configures server features
+ * [WOOKIE-45] - Wookie does not seem to support .html as start files?
+ * [WOOKIE-47] - add required properties to build.properties and add docs
to readme
+ * [WOOKIE-48] - W3C Widgets conformance: incorrect processing of
height/width attributes
+ * [WOOKIE-49] - Error in algorithm for determining the start page for a
widget
+ * [WOOKIE-53] - Eclipse .classpath configuration uses hardcoded local user
path for ivysettings.xml and is missing classpath references to a few
additionally required jars
+ * [WOOKIE-54] - W3C Widgets conformance: incorrect processing of
whitespace and localized elements
+ * [WOOKIE-55] - W3C Widgets conformance: does not support Short name
attribute
+ * [WOOKIE-56] - W3C Widgets conformance: does not correctly handle
language-localized elements
+ * [WOOKIE-58] - W3C Widgets conformance: problems processing icons
+ * [WOOKIE-59] - W3C Widgets conformance: problems processing preferences
+ * [WOOKIE-60] - W3C Widgets conformance: need to fix default identifiers
to support valid IRIs
+ * [WOOKIE-61] - W3C Widgets conformance: problems processing content
elements with inner tags
+ * [WOOKIE-62] - W3C Widgets conformance: treat widget as invalid if it
requires an unsupported feature
+ * [WOOKIE-63] - HibernateException: flush is not valid without active
transaction
+ * [WOOKIE-64] - Wookie rewrites HTML start file incorrectly when injecting
JavaScript: incorrectly encodes inline scripts
+ * [WOOKIE-77] - W3C Widgets conformance: feature name must be a valid IRI
+ * [WOOKIE-78] - W3C Widgets conformance: author href must be a valid URL
+ * [WOOKIE-79] - W3C Widgets conformance: language tags should be verified
+ * [WOOKIE-82] - WARN C3P0ConnectionProvider messages at server runtim
+ * [WOOKIE-83] - Improvements to widget template
+ * [WOOKIE-84] - Remove injected script tags from widget source
+ * [WOOKIE-101] - Binary files are filtered when seeding a widget
+ * [WOOKIE-102] - Javascript can be broken on reformatting
+ * [WOOKIE-105] - Servlet.service() for servlet default threw exception
java.lang.NoSuchMethodError
+ * [WOOKIE-106] - Buildbot gives warnings when running 'ant'
+ * [WOOKIE-107] - warnings when running 'ant compile test'
+ * [WOOKIE-108] - incorrectly named jar when running 'ant jar'
+ * [WOOKIE-109] - Build Failure for 'ant publish-local'
+ * [WOOKIE-113] - Wookie reordering script tags
+ * [WOOKIE-118] - GET and POST request broken (jQuery + Widget.proxify)
+ * [WOOKIE-120] - Testinstallation jetty fails on start on case sensitve
Operationg systems
+ * [WOOKIE-123] - DELETE {wookie}/properties creates property with NULL
value
+ * [WOOKIE-124] - Error when starting development server: cannot run due to
initialisation problem
+ * [WOOKIE-129] - Ant task 'stopserver' does not stop the server
+ * [WOOKIE-136] - Demo of any widget returns 401
+ * [WOOKIE-145] - JPA error when Widget sets preference values
+ * [WOOKIE-148] - Posting XML in the body of a text/xml HTTP request
through the proxy fails
+ * [WOOKIE-157] - Redirected error page has bad links
+ * [WOOKIE-158] - Butterfly widget causes javascript error alert in IE8
+ * [WOOKIE-159] - Old 'basic chat widget' not updating online users when
user navigates away from page
+ * [WOOKIE-160] - Forum widget lists user who posted message as 'No
matching key found'
+ * [WOOKIE-161] - Missing icon in natter widget for user
+ * [WOOKIE-162] - Sharedraw widget has JS errors in IE8
+ * [WOOKIE-163] - Simple chat - typed in messages are being lost
+ * [WOOKIE-164] - Original 'Vote' widget not working
+ * [WOOKIE-165] - Camera widget causes js errors in IE8
+ * [WOOKIE-166] - Geolocation widget causes JS errors in IE8
+ * [WOOKIE-168] - Cannot remove widget from wookie after it has become an
instance.
+ * [WOOKIE-171] - There is a suspected problem with the way the id handler
of the manifest parser is managing odd characters
+ * [WOOKIE-195] - Source and Binary distribution need a few more
disclaimers and notices
+ * [WOOKIE-196] - initDB = True in distribution files
+ * [WOOKIE-197] - readme for WAR is incomplete
+ * [WOOKIE-198] - Standalone binary distribution does not mention 3rd party
license library licenses
+ * [WOOKIE-199] - Unnecessary build directories being created
+ * [WOOKIE-200] - Source distribution is missing MIT license for JQuery
+ * [WOOKIE-202] - Release candidate includes snapshot Jars
+
+Improvements
+============
+ * [WOOKIE-24] - Javadocs still refer to old package names
+ * [WOOKIE-26] - Standalone version of Wookie for development
+ * [WOOKIE-28] - Preview widgets within server application
+ * [WOOKIE-39] - Allow deployment specific properties
+ * [WOOKIE-41] - Enable local configuration of the email server
+ * [WOOKIE-50] - Creation and management of widgets
+ * [WOOKIE-51] - Remove binary widget packages from core server source
+ * [WOOKIE-57] - Use commons-io to replace file util methods
+ * [WOOKIE-69] - deploy-webbapp creates unnecessary interim lib directory
+ * [WOOKIE-70] - Inform the user when an a widget fails to be deployed
using hot-deploy
+ * [WOOKIE-72] - Don't silently swallow exceptions
+ * [WOOKIE-73] - localisation messages are meaningless
+ * [WOOKIE-86] - Configure standalone port
+ * [WOOKIE-87] - Widget template improvements
+ * [WOOKIE-88] - "Friendly" error message to recommend clean-db?
+ * [WOOKIE-91] - Deploy a widget to a running server
+ * [WOOKIE-116] - POST and Basic Auth through proxy
+ * [WOOKIE-125] - Updated PHP framework
+ * [WOOKIE-128] - PHP framework patch
+ * [WOOKIE-130] - Run diagnostic tests on server when starting up
+ * [WOOKIE-135] - Wigets locale changing
+ * [WOOKIE-137] - In CSharp connector all reference to maximize should be
removed.
+ * [WOOKIE-138] - Widgets are not ordered when viewing widget gallery
+ * [WOOKIE-144] - Pluggable Persistence Component
+ * [WOOKIE-153] - Minimal chat widget
+
+New Features
+============
+ * [WOOKIE-33] - testing issues for review subscription
+ * [WOOKIE-85] - Implement W3C Widget Access Request Policy (WARP)
specification
+ * [WOOKIE-99] - Dynamic deployment of Features
+ * [WOOKIE-121] - PHP Connector framework
+ * [WOOKIE-126] - C# Inital framework
+ * [WOOKIE-127] - Python inital framework
+ * [WOOKIE-143] - ActionScript 3.0 / Flex Connector
+
+
+Known Issues
+============
+ * add any other issues outstanding from open 0.9.0 issues
+ TODO * [WOOKIE-**] There is a known issue when using Ant version 1.8.x
to build and run
+ Wookie; you should instead use
version 1.7.1. To check which version
+ of ant you are using, type ant
-version.
+
+
\ No newline at end of file
Copied: incubator/wookie/branches/0.9.x/etc/release/war/WAR_BUILD_NOTES (from
r1087636, incubator/wookie/branches/0.9.x/etc/release/war/README)
URL:
http://svn.apache.org/viewvc/incubator/wookie/branches/0.9.x/etc/release/war/WAR_BUILD_NOTES?p2=incubator/wookie/branches/0.9.x/etc/release/war/WAR_BUILD_NOTES&p1=incubator/wookie/branches/0.9.x/etc/release/war/README&r1=1087636&r2=1089087&rev=1089087&view=diff
==============================================================================
--- incubator/wookie/branches/0.9.x/etc/release/war/README (original)
+++ incubator/wookie/branches/0.9.x/etc/release/war/WAR_BUILD_NOTES Tue Apr 5
15:45:34 2011
@@ -1,5 +1,5 @@
-WAR archive standalone manual configuration
-===========================================
+Apache Wookie - WAR distribution instructions
+==============================================
This folder should contain...
wookie.xml
@@ -10,30 +10,42 @@ NOTICE
LICENSE
README (this file!)
-In order to deploy wookie onto your application server, you must...
+This build is meant to get a user started with the process of deploying
+Wookie under an existing application container and as such Wookie is made
available in
+WAR format. This particular download is oriented towards deploying Wookie
under a Tomcat
+instance running with Mysql. Deploying against other containers and database
environments
+should be also possible by following the instructions below.
+
+Generic instructions for deployment
+===================================
+In order to deploy Wookie onto your application server, you must...
-(1) Install a suitable database driver for wookie on your server (if you
haven't already)
+(1) Install a suitable database driver for Wookie on your server (if you
haven't already)
(2) Create a user with the group/rolename as "widgetadmin" on your server
installation
- and give this user the credentials username=java password=java
(3) Create a database called 'widgetDB' in your database
-(4) Create a user 'java' with the password 'java' in your database and give
this user suitable permissions on the above database
-(5) Run one of the sql scripts found under the scripts folder to create the
wookie database structure
-(6) Create/configure a context.xml file under your server for wookie
+(4) Create a user 'java' with the password 'java' in your database and give
this user suitable
+ permissions on the above database
+(5) Run one of the sql scripts found under the scripts folder to create the
Wookie database structure
+(6) Create/configure a context.xml file under your server for Wookie
(7) Copy the wookie.war to your webapps or deploy directory
(8) Start your server
(9) Open your browser and goto 'http://YOURSERVERADDRESS:8080/wookie' (i.e.
http://localhost:8080/wookie)
-The following text describes this process specifically for tomcat and mysql...
+The following text describes this process specifically for Tomcat and Mysql...
Running Wookie with Tomcat and MySQL manual configuration
=========================================================
(1) Obtain a JDBC driver jar file for the database.
- (for example the mysql driver can be downloaded from
http://www.mysql.com/downloads/connector/j/)
- The downloaded zip file should contain a jar file, something similar to
mysql-connector-java-5.1.*-bin.jar
+ (for example the mysql driver can be downloaded from
+ http://www.mysql.com/downloads/connector/j/)
+ The downloaded zip file should contain a jar file, something similar to
+ mysql-connector-java-5.1.*-bin.jar
-(2) Place the mysql-connector-java-5.1.*-bin.jar file into tomcats lib folder
so it is founnd on the classpath at runtime
+(2) Place the mysql-connector-java-5.1.*-bin.jar file into tomcats lib folder
+ so it is founnd on the classpath at runtime
(for example in tomcat 5.5.* place this file into
/tomcat-root/common/lib)
(for example in tomcat 6.0.* place this file into /tomcat-root/lib)
@@ -44,13 +56,16 @@ Running Wookie with Tomcat and MySQL man
(4) Create a database in mysql called 'widgetdb'.
-(5) Create a user in mysql 'java' with the password 'java' and give them
suitable permisions on the widgetDB
+(5) Create a user in mysql 'java' with the password 'java' and give them
suitable permisions
+ on the widgetDB
(6) Copy the file wookie.xml to your tomcat-root/conf/catalina/servername
folder
(for example in tomcat 5.5.* & 6.0.* place this file into
/tomcat-root/conf/Catalina/localhost)
-(7) Locate the 'mysql-wookie-schema.sql' file found under 'scripts' and run
this to populate the 'widgetDB' database you created
- - NOTE: the first time you run this script, you may have to remove the
drop foreign key statements found at the top of the script
+(7) Locate the 'mysql-wookie-schema.sql' file found under 'scripts' and run
this to populate the
+ 'widgetDB' database you created
+ - NOTE: the first time you run this script, you may have to remove the
drop foreign key statements
+ found at the top of the script
i.e. the statements that look similar to these..
