svn commit: r168651 - /incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml

[ky...@apache.org]

Author: kylem
Date: Fri May  6 13:54:23 2005
New Revision: 168651

URL: http://svn.apache.org/viewcvs?rev=168651&view=rev
Log:
Fix syntax issue in last docs submission that failed validation.  'ant validate' now passes.

Modified:
    incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml

Modified: incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml
URL: http://svn.apache.org/viewcvs/incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml?rev=168651&r1=168650&r2=168651&view=diff
==============================================================================
--- incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml (original)
+++ incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsProgramming.xml Fri May  6 13:54:23 2005
@@ -907,7 +907,7 @@
         </section>
         <section>
             <title>Inheritance</title>
-            <p>The Controls architecture also makes it possible to extend the functionality of existing Controls using standard Java inheritance.   While more complex scenarios are possible, a common model for extending a Control type using inheritance involves extending both public interface <b>and</b> the implementation to extend base functionality by adding new operations, events, or properties.</p>
+            <p>The Controls architecture also makes it possible to extend the functionality of existing Controls using standard Java inheritance.   While more complex scenarios are possible, a common model for extending a Control type using inheritance involves extending both public interface and the implementation to extend base functionality by adding new operations, events, or properties.</p>
 <p>The following code sample shows the basic structure:</p>
 <p><strong>Basic Inheritance Sample Code</strong></p>
 <source>
@@ -931,8 +931,7 @@
 
 <p>In the example above, the BBean JavaBean class that results from processing of B.java will expose the operations, properties, and events defined by both the A and B control interfaces.  The BImpl class would need to implement all operations defined by the B interface, and could also choose to override some, all, or none of the operations defined by A.</p>
 
-<p>Inheritance is also supported for extensible control types.  If AImpl implements the Extensible interface, then BImpl could choose to define additional extensibility PropertySets and implement a new Extensible.invoke() method to provide their semantics (delegating to AImpl.invoke() as approriate). It could also choose not to extend the extensibilty semantics and allow all operations defined within a ControlExtension derived from B to be handled by AImpl.invoke().
-</p>
+<p>Inheritance is also supported for extensible control types.  If AImpl implements the Extensible interface, then BImpl could choose to define additional extensibility PropertySets and implement a new Extensible.invoke() method to provide their semantics (delegating to AImpl.invoke() as approriate). It could also choose not to extend the extensibilty semantics and allow all operations defined within a ControlExtension derived from B to be handled by AImpl.invoke().</p>
 
         </section>