svn commit: r386098 - /cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java

[cz...@apache.org]

Author: cziegeler
Date: Wed Mar 15 07:49:44 2006
New Revision: 386098

URL: http://svn.apache.org/viewcvs?rev=386098&view=rev
Log:
Add some important comments

Modified:
    cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java

Modified: cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java
URL: http://svn.apache.org/viewcvs/cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java?rev=386098&r1=386097&r2=386098&view=diff
==============================================================================
--- cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java (original)
+++ cocoon/branches/BRANCH_2_1_X/src/blocks/portal/java/org/apache/cocoon/portal/event/Receiver.java Wed Mar 15 07:49:44 2006
@@ -33,7 +33,12 @@
  *
  * If a receiver is interested in more than one event type, then it can implement
  * several inform methods each with the corresponding event class as the first
- * parameter.
+ * parameter. However, it is important to notice that the current implementation
+ * of the event manager has some restrictions! A receiver should not implement to
+ * inform methods where one event is a subclass or subinterface of the other event.
+ * In that case only one method is called and it's not deterministic which one will be called
+ * (this may vary for example on the used operating system the code runs on!).
+ * This problem will be solved in 2.2.
  *
  * @author <a href="mailto:cziegeler@apache.org">Carsten Ziegeler</a>
  *