[weld-commits] Weld SVN: r4924 - doc/trunk/reference/en-US.

[weld-commits at lists.jboss.org]

Author: gavin.king at jboss.com
Date: 2009-11-09 20:55:19 -0500 (Mon, 09 Nov 2009)
New Revision: 4924

Modified:
   doc/trunk/reference/en-US/scopescontexts.xml
Log:
better

Modified: doc/trunk/reference/en-US/scopescontexts.xml
===================================================================
--- doc/trunk/reference/en-US/scopescontexts.xml	2009-11-10 01:49:00 UTC (rev 4923)
+++ doc/trunk/reference/en-US/scopescontexts.xml	2009-11-10 01:55:19 UTC (rev 4924)
@@ -312,20 +312,15 @@
          <title>The <literal>@New</literal> qualifier</title>
 
          <para>
-            The built-in <literal>@New</literal> qualifier annotation allows <emphasis>implicit</emphasis> definition of
-            a dependent bean at an injection point. Suppose we declare the following injected field:
+            The built-in qualifier <literal>@New</literal> allows us to obtain a dependent object of a specified class.
          </para>
 
          <programlisting role="JAVA"><![CDATA[@Inject @New Calculator calculator;]]></programlisting>
-
+         
+         <para>The class must be a valid managed bean or session bean, but need not be an enabled bean.</para>
+         
          <para>
-            Then a bean with scope <literal>@Dependent</literal>, qualifier type <literal>@New</literal>, API type
-            <literal>Calculator</literal>, implementation class <literal>Calculator</literal> and deployment type
-            <literal>@Standard</literal> is implicitly defined.
-         </para>
-
-         <para>
-            This is true even if <literal>Calculator</literal> is <emphasis>already</emphasis> declared with a different
+            This works even if <literal>Calculator</literal> is <emphasis>already</emphasis> declared with a different
             scope type, for example:
          </para>