[weld-commits] Weld SVN: r4673 - doc/trunk/reference/en-US.
weld-commits at lists.jboss.org
weld-commits at lists.jboss.org
Wed Nov 4 14:20:00 EST 2009
Author: dan.j.allen
Date: 2009-11-04 14:19:59 -0500 (Wed, 04 Nov 2009)
New Revision: 4673
Modified:
doc/trunk/reference/en-US/ee.xml
doc/trunk/reference/en-US/environments.xml
doc/trunk/reference/en-US/events.xml
doc/trunk/reference/en-US/injection.xml
doc/trunk/reference/en-US/interceptors.xml
doc/trunk/reference/en-US/part3.xml
doc/trunk/reference/en-US/scopescontexts.xml
Log:
fix mdashes
note about dashes in readme
Modified: doc/trunk/reference/en-US/ee.xml
===================================================================
--- doc/trunk/reference/en-US/ee.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/ee.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -206,7 +206,7 @@
<title>Packaging and deployment</title>
<para>
- CDI doesn't define any special deployment archive. You can package beans in JARs, EJB-JARs or WARs — any
+ CDI doesn't define any special deployment archive. You can package beans in JARs, EJB-JARs or WARs — any
deployment location in the application classpath. However, the archive must be a "bean archive". That means
each archive that contains beans <emphasis>must</emphasis> include a file named <literal>beans.xml</literal> in
the <literal>META-INF</literal> directory of the classpath or <literal>WEB-INF</literal> directory of the web
Modified: doc/trunk/reference/en-US/environments.xml
===================================================================
--- doc/trunk/reference/en-US/environments.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/environments.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -79,6 +79,7 @@
jars:
</para>
+ <!-- TODO check for accuracy in 1.0 release -->
<itemizedlist>
<listitem>
<para>
Modified: doc/trunk/reference/en-US/events.xml
===================================================================
--- doc/trunk/reference/en-US/events.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/events.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -105,7 +105,7 @@
<programlisting role="JAVA"><![CDATA[public void afterDocumentUpdate(@Observes @Updated Document document) { ... }]]></programlisting>
<para>
- An observer method need not specify any event qualifiers — in this case it is interested in
+ An observer method need not specify any event qualifiers — in this case it is interested in
<emphasis>all</emphasis> events of a particular type. If it does specify event bindings, it's only interested
in events which also have those qualifiers.
</para>
Modified: doc/trunk/reference/en-US/injection.xml
===================================================================
--- doc/trunk/reference/en-US/injection.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/injection.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -381,7 +381,7 @@
<para>
To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide a bean which implements the bean
- type and has all the qualifier types of the injection point — or explicitly enable an
+ type and has all the qualifier types of the injection point — or explicitly enable an
<literal>@Alternative</literal> bean that implements the bean type and has the appropriate qualifier types.
</para>
Modified: doc/trunk/reference/en-US/interceptors.xml
===================================================================
--- doc/trunk/reference/en-US/interceptors.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/interceptors.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -278,7 +278,7 @@
<para>
Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type
with other interceptor binding types (termed a <emphasis>meta-annotation</emphasis>). The interceptor bindings
- are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as
+ are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as
meta-annotations.
</para>
@@ -322,7 +322,7 @@
</listitem>
<listitem>
<para>
- the interceptor ordering is non-global — it is determined by the order in which interceptors are
+ the interceptor ordering is non-global — it is determined by the order in which interceptors are
listed at the class level.
</para>
</listitem>
Modified: doc/trunk/reference/en-US/part3.xml
===================================================================
--- doc/trunk/reference/en-US/part3.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/part3.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -10,7 +10,7 @@
<para>
You don't see string-based identifiers in CDI code, not because the framework is hiding them from you using clever
- defaulting rules — so-called "configuration by convention" — but because there are simply no strings
+ defaulting rules — so-called "configuration by convention" — but because there are simply no strings
there to begin with!
</para>
Modified: doc/trunk/reference/en-US/scopescontexts.xml
===================================================================
--- doc/trunk/reference/en-US/scopescontexts.xml 2009-11-04 19:12:45 UTC (rev 4672)
+++ doc/trunk/reference/en-US/scopescontexts.xml 2009-11-04 19:19:59 UTC (rev 4673)
@@ -267,7 +267,7 @@
<para>
The container is permitted to destroy a conversation and all state held in its context at any time in order
to preserve resources. A CDI implementation will normally do this on the basis of some kind of timeout
- — though this is not required by the CDI specification. The timeout is the period of inactivity before
+ — though this is not required by the CDI specification. The timeout is the period of inactivity before
the conversation is destroyed (as opposed to the amount of time the conversation is active).
</para>
More information about the weld-commits
mailing list