You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by ha...@apache.org on 2002/04/07 10:54:40 UTC
cvs commit: jakarta-avalon-site/docs/framework separation-of-interface-and-implementation.html
hammant 02/04/07 00:54:40
Modified: docs/framework
separation-of-interface-and-implementation.html
Log:
correct typos
Revision Changes Path
1.3 +5 -5 jakarta-avalon-site/docs/framework/separation-of-interface-and-implementation.html
Index: separation-of-interface-and-implementation.html
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/docs/framework/separation-of-interface-and-implementation.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- separation-of-interface-and-implementation.html 2 Apr 2002 17:21:17 -0000 1.2
+++ separation-of-interface-and-implementation.html 7 Apr 2002 08:54:40 -0000 1.3
@@ -250,7 +250,7 @@
this too could be confusing as the aforementioned SAX is not quite a
pure set of interfaces. It has a static factory that thunks in an
implementation that all subsequent calls to the factory method will be
- forced to use. See Anto-patterns below.
+ forced to use. See Anti-patterns below.
</p>
<p align="justify">
@@ -348,8 +348,8 @@
<p align="justify">
The central message of this is that it you have interface/impl separated your
tool, and are doing tricky things with more classloaders in the implementation,
- please make sure ytou do not assume that the parent classloader of any classloader
- is the system classoader. If your reusable tool has been taken by another team
+ please make sure you do not assume that the parent classloader of any classloader
+ is the system classloader. If your reusable tool has been taken by another team
and at some non root place in a classloader tree, then the tools will fail if
you have made such assumptions.
</p>
@@ -373,8 +373,8 @@
SAX, mentioned in multiple contexts in this document, is also an example of
where the design can go wrong. The Factory is static (that in itself is an
anti-pattern to IoC). Despite giving the appearance of having the ability
- to generate a parsr based on the impl's class name, only the first caller
- of that method will regsiter a parser for the whole environment to use.
+ to generate a parser based on the implementation's class name, only the first
+ caller of that method will register a parser for the whole environment to use.
</p>
<p align="justify">
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>