Revision: 1511
Author: [email protected]
Date: Tue Mar  1 05:25:59 2011
Log: Updating javadoc to indicate that a binding is required when using SimpleScope.

Also battled with {@code } and <code>. Obviously did the wrong thing here, but wiki preview is not helping me, if I had an excuse.
http://code.google.com/p/google-guice/source/detail?r=1511

Modified:
 /wiki/CustomScopes.wiki

=======================================
--- /wiki/CustomScopes.wiki     Tue Apr 14 18:27:23 2009
+++ /wiki/CustomScopes.wiki     Tue Mar  1 05:25:59 2011
@@ -34,7 +34,7 @@

 /**
  * Scopes a single execution of a block of code. Apply this scope with a
- * try/finally block: <pre>   {@code
+ * try/finally block: <pre><code>
  *
  *   scope.enter();
  *   try {
@@ -44,21 +44,19 @@
  *   } finally {
  *     scope.exit();
  *   }
- * }</pre>
+ * </code></pre>
  *
  * The scope can be initialized with one or more seed values by calling
  * <code>seed(key, value)</code> before the injector will be called upon to
* provide for this key. A typical use is for a servlet filter to enter/exit the
  * scope, representing a Request Scope, and seed HttpServletRequest and
- * HttpServletResponse. For each key inserted with seed(), it's good practice
- * (since you have to provide <i>some</i> binding anyhow) to include a
- * corresponding binding that will throw an exception if Guice is asked to
- * provide for that key if it was not yet seeded: <pre>   {@code
- *
+ * HttpServletResponse. For each key inserted with seed(), you must include a
+ * corresponding binding:
+ *  <pre><code>
  *   bind(key)
- *       .toProvider(SimpleScope.<KeyClass>seededKeyProvider())
+ *       .toProvider(SimpleScope.&lt;KeyClass&gt;seededKeyProvider())
  *       .in(ScopeAnnotation.class);
- * }</pre>
+ * </code></pre>
  *
  * @author Jesse Wilson
  * @author Fedor Karpelevitch

--
You received this message because you are subscribed to the Google Groups 
"google-guice-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-guice-dev?hl=en.

Reply via email to