Author: vanto
Date: Mon Dec 31 19:00:15 2012
New Revision: 1427223
URL: http://svn.apache.org/viewvc?rev=1427223&view=rev
Log:
fix formatting.
Modified:
ode/site/trunk/content/custom-xpath-functions.mdtext
Modified: ode/site/trunk/content/custom-xpath-functions.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/custom-xpath-functions.mdtext?rev=1427223&r1=1427222&r2=1427223&view=diff
==============================================================================
--- ode/site/trunk/content/custom-xpath-functions.mdtext (original)
+++ ode/site/trunk/content/custom-xpath-functions.mdtext Mon Dec 31 19:00:15
2012
@@ -15,7 +15,7 @@ An extension function is invoked using a
Extension functions must be implemented in Java. You bind external Java
classes by encoding the class name part in the namespace URI. The URI for the
namespace identifies the class where the external function will be found. The
namespace URI must be ```java:``` followed by the fully-qualified class name;
for example ```xmlns:date="java:java.util.Date"```). The class must be on the
classpath, or more specifically accessible from the current classloader.
<div class="alert">
-Saxon 8.x and earlier supported namespace binding with a training ```/``` +
the fully-qualified class name; for example
```xmlns:date="http://www.jclark.com/xt/java/java.util.Date"```). This approach
is no longer supported in Saxon 9.x and you should now use the ```java:```
prefix.
+Saxon 8.x and earlier supported namespace binding with a training "/" + the
fully-qualified class name; for example
<code>xmlns:date="http://www.jclark.com/xt/java/java.util.Date";</code>). This
approach is no longer supported in Saxon 9.x and you should now use the
<code>java:</code> prefix.
</div>
:::xml
