This is an automated email from the ASF dual-hosted git repository.
garydgregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-ognl.git
The following commit(s) were added to refs/heads/master by this push:
new b516ebd Normalize spelling
b516ebd is described below
commit b516ebdc49cb488c82130634f5a90c554bba2849
Author: Gary Gregory <[email protected]>
AuthorDate: Sat Jul 4 19:23:56 2026 -0400
Normalize spelling
---
src/site/xdoc/developer-guide.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/site/xdoc/developer-guide.xml
b/src/site/xdoc/developer-guide.xml
index 5b22558..3ebd34b 100644
--- a/src/site/xdoc/developer-guide.xml
+++ b/src/site/xdoc/developer-guide.xml
@@ -243,7 +243,7 @@ Ognl.setValue( "identifiers",
</section>
<section name="Null Handler">
- <p>When navigating a chain sometimes properties or methods will
evaluate to null, causing subsequent properties or method calls to fail with
<code>NullPointerException</code>s. Most of the time this behaviour is correct
(as it is
+ <p>When navigating a chain sometimes properties or methods will
evaluate to null, causing subsequent properties or method calls to fail with
<code>NullPointerException</code>s. Most of the time this behavior is correct
(as it is
with Java), but sometimes you want to be able to dynamically
substitute another object in place of <code>null</code>. The
<code>NullHandler</code> interface allows you to specify on a class-by-class
basis how nulls are
handled within OGNL expressions. Implementing this interface allows
you to intercept when methods return <code>null</code> and properties evaluate
to <code>null</code> and allow you to substitute a new value. Since you are
given the source of the method or property a really clever implementor
might write the property back to the object so that subsequent invocations do
not return or evaluate to <code>null</code>.</p>
