Author: hlship
Date: Wed Aug 10 17:02:04 2011
New Revision: 1156263
URL: http://svn.apache.org/viewvc?rev=1156263&view=rev
Log:
Correct a typo
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/SymbolConstants.java
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/SymbolConstants.java
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/SymbolConstants.java?rev=1156263&r1=1156262&r2=1156263&view=diff
==============================================================================
---
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/SymbolConstants.java
(original)
+++
tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/SymbolConstants.java
Wed Aug 10 17:02:04 2011
@@ -328,7 +328,7 @@ public class SymbolConstants
/**
* The fix for <a
href="https://issues.apache.org/jira/browse/TAP5-1596";>TAP5-1596</a> means that
component ids referenced
- * by event handler methods (either the nameing convention, or the {@link
org.apache.tapestry5.annotations.OnEvent} annotation)
+ * by event handler methods (either the naming convention, or the {@link
org.apache.tapestry5.annotations.OnEvent} annotation)
* can cause a page load error if there is no matching component in the
component's template. Although this is correct behavior,
* it can make the upgrade from 5.2 to 5.3 difficult if an existing app
had some "left over" event handler methods. Changing
* this symbol to {@code false} is a temporary approach to resolving this
problem.
