Author: buildbot
Date: Thu Jul 25 13:12:41 2013
New Revision: 871154
Log:
Staging update by buildbot for sis
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/faq.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 25 13:12:41 2013
@@ -1 +1 @@
-1506953
+1506956
Modified: websites/staging/sis/trunk/content/faq.html
==============================================================================
--- websites/staging/sis/trunk/content/faq.html (original)
+++ websites/staging/sis/trunk/content/faq.html Thu Jul 25 13:12:41 2013
@@ -86,7 +86,7 @@
<li><a href="#metadata">Metadata</a><ul>
<li><a href="#metadata-implementation">Custom implementations</a><ul>
<li><a href="#metadata-proxy">My metadata are stored in a database-like framework.
Implementing every GeoAPI interfaces for them is impractical.</a></li>
-<li><a href="#i-cant-marshall-my-custom-implementation-jaxbexception-metadata-unknownclass">I
can't marshall my custom implementation (JAXBException). {#metadata-unknownClass"}</a></li>
+<li><a href="#i-cant-marshall-my-custom-implementation-metadata-unknownclass">I
can't marshall my custom implementation. {#metadata-unknownClass"}</a></li>
</ul>
</li>
</ul>
@@ -104,9 +104,9 @@
<h3 id="metadata-proxy">My metadata are stored in a database-like framework. Implementing
every GeoAPI interfaces for them is impractical.</h3>
<p>Developers do not need to implement directly the metadata interfaces.
If the underlying storage framework can access metadata from their class and attribute names
(either Java names
-or ISO/OGC names), then it is possible to implement a single engine accessing any kind of
metadata and let the
+or <abbr title="International Organization for Standardization">ISO</abbr>/<abbr
title="Open Geospatial Consortium">OGC</abbr> names), then it is possible to implement
a single engine accessing any kind of metadata and let the
Java Virtual Machine implements the GeoAPI interfaces on-the-fly, using the <code>java.lang.reflect.Proxy</code>
class.
-See the <code>Proxy</code> Javadoc for details, keeping in mind that the ISO/OGC
name of a <code>java.lang.Class</code> or
+See the <code>Proxy</code> Javadoc for details, keeping in mind that the <abbr
title="International Organization for Standardization">ISO</abbr>/<abbr title="Open
Geospatial Consortium">OGC</abbr> name of a <code>java.lang.Class</code>
or
<code>java.lang.reflect.Method</code> object can be obtained as below:</p>
<div class="codehilite"><pre><span class="n">UML</span> <span
class="n">uml</span> <span class="o">=</span> <span class="n">method</span><span
class="o">.</span><span class="na">getAnnotation</span><span class="o">(</span><span
class="n">UML</span><span class="o">.</span><span class="na">class</span><span
class="o">);</span>
<span class="k">if</span> <span class="o">(</span><span class="n">uml</span>
<span class="o">!=</span> <span class="kc">null</span><span class="o">)</span>
<span class="o">{</span>
@@ -118,7 +118,7 @@ See the <code>Proxy</code> Javadoc for d
<p>This is indeed the approach taken by the <code>org.apache.sis.metadata.sql</code>
package for providing an implementation
of all GeoAPI metadata interfaces reading their values directly from a SQL database.</p>
-<h3 id="i-cant-marshall-my-custom-implementation-jaxbexception-metadata-unknownclass">I
can't marshall my custom implementation (<code>JAXBException</code>). {#metadata-unknownClass"}</h3>
+<h3 id="i-cant-marshall-my-custom-implementation-metadata-unknownclass">I can't marshall
my custom implementation. {#metadata-unknownClass"}</h3>
<p>The classes given to the JAXB marshaller shall contain JAXB annotations,
otherwise the following exception is thrown:</p>
<div class="codehilite"><pre>javax.xml.bind.JAXBException: class MyCustomClass
|