/usr/share/doc/libognl-java/DeveloperGuide/classReferences.html is in libognl-java-doc 2.7.3-5.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 | <html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. Class References</title><link href="../docbook.css" type="text/css" rel="stylesheet"><meta content="DocBook XSL Stylesheets V1.78.1" name="generator"><link rel="home" href="index.html" title="OGNL Developer Guide"><link rel="up" href="index.html" title="OGNL Developer Guide"><link rel="prev" href="elementsAccessors.html" title="Chapter 4. Elements Accessors"><link rel="next" href="typeConversion.html" title="Chapter 6. Type Conversion"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 5. Class References</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="elementsAccessors.html"><img src="../images/navigation/prev.gif" alt="Prev"></a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="typeConversion.html"><img src="../images/navigation/next.gif" alt="Next"></a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="classReferences"></a>Chapter 5. Class References</h1></div></div></div><p>In the sections on accessing static field and static methods it stated that classes must be full-specified in between the class reference specifier (<code class="constant">@</code><code class="classname"><classname></code><code class="constant">@</code><span class="property"><field|method></span><code class="constant">@</code>).
This is not entirely true; the default <code class="classname">ClassResolver</code> simply looks up the name of the class and assumes that it is fully specified. The <code class="classname">ClassResolver</code> interface is included in the
<acronym class="acronym">OGNL</acronym> context to perform lookup of classes when an expression is evaluated. This makes it possible to specify, for example, a list of imports that are specific to a particular <code class="function">setValue()</code> or
<code class="function">getValue()</code> context in order to look up classes. It also makes class references agreeably short because you don't have to full specify a class name.</p><pre class="programlisting">public interface ClassResolver
{
public Class classForName(Map context, String className) throws ClassNotFoundException;
}</pre><p>You can set a class resolver on a context basis using the <code class="classname">Ognl</code> methods <code class="methodname">addDefaultContext()</code> and <code class="methodname">createDefaultContext()</code>.</p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="elementsAccessors.html"><img src="../images/navigation/prev.gif" alt="Prev"></a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="typeConversion.html"><img src="../images/navigation/next.gif" alt="Next"></a></td></tr><tr><td valign="top" align="left" width="40%">Chapter 4. Elements Accessors </td><td align="center" width="20%"><a accesskey="h" href="index.html"><img src="../images/navigation/home.gif" alt="Home"></a></td><td valign="top" align="right" width="40%"> Chapter 6. Type Conversion</td></tr></table></div></body></html>
|