Index: modperl-docs/src/docs/2.0/api/Apache2/Reload.pod
===================================================================
--- modperl-docs/src/docs/2.0/api/Apache2/Reload.pod	(revision 390466)
+++ modperl-docs/src/docs/2.0/api/Apache2/Reload.pod	(working copy)
@@ -326,6 +326,75 @@
 Solution 2: remember to touch the script itself every time you change
 the module that it requires.
 
+=head2 Problems with Changing Package Methods
+
+=head3 The Problem
+
+If you subclass a module to override a few methods, and then decide to 
+remove a subclassed method (and call off the method in the parent class 
+instead), you will raise an error instead of calling the parent method.
+If you do a restart, everything works as expected.
+
+Let's say that there is an OOP module C<My::Utils> with a C<color> method:
+
+  #module:My/Utils.pm
+  #----------------
+  package MyUtils;
+  	# snip
+  sub color { "white" }
+  1;
+
+And it is subclassed by C<My::Utils::Customized>:
+
+  #module:My::Utils::Customized
+  #------------
+  package My::Utils::Customized;
+  	# snip
+  sub color { "red" }
+  1;
+
+And we have a mod_perl handler that addresses this:
+
+  #file:handler.pl
+  #------------
+  use My::Utils;
+  use My::Utils::Customized;
+  sub handler
+  {
+  	# snip
+  	$myObject = My::Utils::Customized->new();
+  	$r->print( "The color is " $myObject->color() );
+  	# snip
+  }
+
+If we run the handler for the first time and we get the response:
+
+  The color is red
+
+Now we change C<My::Utils::Customized>:
+
+  -  sub color { "red" }
+
+And issue the request again. C<Apache2::Reload> does its job and we can
+see that C<My::Utils> was reloaded (look in the I<error_log>
+file). However the script now returns:
+
+  Not a code reference at ...
+
+If we restart Apache, we will see
+
+  The color is white
+
+=head3 The Explanation
+
+ModPerl caches method lookups in order to reduce the performance hit of OO
+code.  Apache::Reload can not handle changes that modify which package a 
+method should be called in.
+
+=head3 The Solution
+
+For now, restart Apache.  A future patch may solve this particularity.
+
 =head1 Threaded MPM and Multiple Perl Interpreters
 
 If you use C<Apache2::Reload> with a threaded MPM and multiple Perl
