Author: scottbw
Date: Thu Oct 13 17:18:28 2011
New Revision: 1182995
URL: http://svn.apache.org/viewvc?rev=1182995&view=rev
Log:
Removed fixed issues, added WOOKIE-222
Modified:
incubator/wookie/site/trunk/content/wookie/docs/faq.mdtext
Modified: incubator/wookie/site/trunk/content/wookie/docs/faq.mdtext
URL:
http://svn.apache.org/viewvc/incubator/wookie/site/trunk/content/wookie/docs/faq.mdtext?rev=1182995&r1=1182994&r2=1182995&view=diff
==============================================================================
--- incubator/wookie/site/trunk/content/wookie/docs/faq.mdtext (original)
+++ incubator/wookie/site/trunk/content/wookie/docs/faq.mdtext Thu Oct 13
17:18:28 2011
@@ -40,42 +40,21 @@ Note: as widget.proxify() is not part of
Wookie implements the localization model described in the [W3C Widgets:
Packaging and Configuration][1] specification. This means that Widgets contain
"locale" folders for specific locales (eg. "/locales/et/index.html"), and
Wookie will serve resources in matching locale folders in preference to generic
resources. Wookie uses the 'locale' parameter of a request for a new widget as
the preferred locale for resource requests; if this is absent then Wookie uses
the server's default locale as picked up through system settings. We use
[ICU4J][2] for all locale processing, including locating system defaults.
-# Wookie messed up my widget's `<script>` tags when I imported it! What
happened?
-
-Wookie uses HtmlCleaner to inject its own script tags into your Widget's start
file when it is uploaded. This works fine in most cases; however if you use
_self-closing script tags_ things can go wrong. To avoid this always use
regular HTML-style script tags e.g `<script src="main.js"></script>` and not
`<scripr src="main.js"/>`. See [Issue WOOKIE-42][3] for more information.
-
# When I run Wookie in Tomcat I get a "java.security.AccessControlException:
access denied (java.util.PropertyPermission user.dir read)"
-This problem occurs when the security manager is enabled in Tomcat, but
without the proper permission assigned for Wookie. There is documentation that
can help you define the security policy properly in section on [Running
Wookie][4].
-
-# Wookie installs fine in Tomcat, but when I try to see it I get
"org.hibernate.HibernateException: flush is not valid without active
transaction"
-
-This problem occurs when running Tomcat with Security Manager enabled, but
without having granted permissions for Wookie to access the database server.
For development purposes its better to just run Tomcat without Security Manager
enabled; otherwise you need to edit your catalina.policy file as described in
the [Tomcat Security Manager How-To][5].
+This problem occurs when the security manager is enabled in Tomcat, but
without the proper permission assigned for Wookie. There is documentation that
can help you define the security policy properly in section on [Running
Wookie][3].
# Wookie throws a
"java.lang.NoSuchMethodError:javax.servlet.ServletContext.getContextPath()"
exception when I try to load a widget
-This problem occurs in version of Apache Tomcat that do not support the
current Servlet specification; to avoid this error update to Tomcat 6.0 or
higher. See [Issue WOOKIE-105][6] for more information
-
-# I shut down my Wookie and now when I try to run it I get an error. How do I
run it again?
-
-Whenever you execute the `ant run` command to run Wookie in standalone
(developer) mode, the database is recreated. This means that if you stop and
re-run Wookie you'll get an error message. To avoid this problem use `ant
clean-db run` instead.
-
+This problem occurs in version of Apache Tomcat that do not support the
current Servlet specification; to avoid this error update to Tomcat 6.0 or
higher. See [Issue WOOKIE-105][4] for more information
# Why can't I add any widgets, either through the admin interface or by
dropping them into the deploy folder?
One of the most common reasons for this is that the application doesn't have
permission to write to the wookie/wservices directory, which is where Wookie
expands widgets when they are uploaded. For example, if you are deploying
Wookie on Tomcat, make sure webapps/wookie is owned by the tomcat user and not
by root.
-# Why do I get an error message like `"wookie\widgets\bubbles\widgets\bubbles
does not exist"` when I try to build Wookie?
-
-This problem occurs when building Wookie using Ant 1.8.x. The build will work
fine if you use Ant 1.7.1. See [Issue WOOKIE-152][7] for more information
-
-# Why doesn't my script run using JQuery's `$(document).ready` ?
-
-This is a known issue. See [Issue WOOKIE-90][8] for more information. As a
workaround you can use `<body onload="...">`
-
# My widgets do not seem to be updating the preference data in wookie
-This is a known issue. See [Issue WOOKIE-44][9] for more information. This
problem typically occurs when using Internet Explorer (version 8 and less). It
is only flagged here as a warning because depending on how the widget calls the
widget javascript API, you may or may not encounter a problem. In essence
there are two ways of setting a preference in your widgets javascript
implementation...
+This is a known issue. See [Issue WOOKIE-44][5] for more information. This
problem typically occurs when using Internet Explorer (version 8 and less). It
is only flagged here as a warning because depending on how the widget calls the
widget javascript API, you may or may not encounter a problem. In essence
there are two ways of setting a preference in your widgets javascript
implementation...
(1) widget.preferences.setItem("foo", "bar");
(2) widget.preferences.foo = "bar";
@@ -95,12 +74,27 @@ Other browsers should be unaffected by t
If your widget does not have an id defined in the widget's config.xml file or
the id is not a valid URI then wookie will load but not update your
widget. If this is the case then (for the moment) you will need to
manually remove the old version of the widget using wookie's admin page.
+# Why do I get a dialog box saying "session error" when I try to view my
widget?
+
+There is a known issue when using Tomcat 7.* with Wookie (see
[WOOKIE-222][6]). 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.)
+
+
[1]: http://www.w3.org/TR/widgets/#internationalization-and-localization
[2]: http://site.icu-project.org/
- [3]: http://issues.apache.org/jira/browse/WOOKIE-42
- [4]: developer/running.html#running_wookie_with_a_security_manager
- [5]: http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html
- [6]: https://issues.apache.org/jira/browse/WOOKIE-105
- [7]: https://issues.apache.org/jira/browse/WOOKIE-152
- [8]: https://issues.apache.org/jira/browse/WOOKIE-90
- [9]: https://issues.apache.org/jira/browse/WOOKIE-44
\ No newline at end of file
+ [3]: developer/running.html#running_wookie_with_a_security_manager
+ [4]: https://issues.apache.org/jira/browse/WOOKIE-105
+ [5]: https://issues.apache.org/jira/browse/WOOKIE-44
+ [6]: https://issues.apache.org/jira/browse/WOOKIE-222
\ No newline at end of file
