Author: [email protected]
Date: Tue Apr 14 15:15:57 2009
New Revision: 5233
Modified:
wiki/ResourceOracle.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/ResourceOracle.wiki
==============================================================================
--- wiki/ResourceOracle.wiki (original)
+++ wiki/ResourceOracle.wiki Tue Apr 14 15:15:57 2009
@@ -93,4 +93,26 @@
# If no resources change during the refresh, the identities of all the
Collections exposed by the {{{ResourceOracleImpl}}} remains the same.
# If any of the previous resource does not change during the refresh, its
identity remains the same.
-During a refresh, as a first step, the resource map is recomputed. If none
of the resources in the map have changed, the previous collections are kept
as is. This guarantees invariant 1. Furthermore, if a resource has not
changed, the old resource is used instead of the new resource, thus
guaranteeing invariant 2.
\ No newline at end of file
+During a refresh, as a first step, the resource map is recomputed. If none
of the resources in the map have changed, the previous collections are kept
as is. This guarantees invariant 1. Furthermore, if a resource has not
changed, the old resource is used instead of the new resource, thus
guaranteeing invariant 2.
+
+==When multiple {{{PathPrefix}}}es have the same path==
+_(Note: As of Gwt 1.6, this section has not been implemented)_
+
+As of Gwt 1.6, if multiple {{{PathPrefix}}}es have the same path attribute
but different {{{ResourceFilter}}}s, only the last one was kept. This is an
undesirable outcome in most cases. For example, if there are two
{{{PathPrefix}}}es p4 and p5:
+{{{
+p4:<source path="client" includes="*.java" excludes="**/testing/***" />
+
+p5: <source path="client" includes="Foo.java" excludes="shared/**" />
+}}}
+
+only the second path-prefix is kept. In particular, a path like
client/Bar.java will be excluded by the second path-prefix, which is
probably different from what the user wanted. With Gwt 1.6, when a resource
with a specified path is processed by a {{{PathPrefix}}}, the output is
either include or exclude.
+
+
+To handle multiple {{{PathPrefix}}}es meaningfully, we generalize the
output of a {{{PathPrefix}}}. When a resource is processed by a
{{{PathPrefix}}}, the output can be:
+
+ # *include*: if its include filter specifically includes the resource
and its exclude filter does not excludes the resource
+ # *exclude*: if its exclude filter specifically excludes the resource
+ # *unspecified_include*: if the resource is included by default
+ # *unspecified_exclude*: if the resource is excluded just by default
+
+
\ No newline at end of file
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
