Author: mac
Date: Tue Aug 30 02:10:31 2005
New Revision: 264745
URL: http://svn.apache.org/viewcvs?rev=264745&view=rev
Log:
link tags -> a tags
Modified:
webservices/jaxme/branches/MAVEN/projects/js/xdocs/apps/xmlrpc.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/index.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/jparser.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/chains.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/proxy.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/versioning.xml
webservices/jaxme/branches/MAVEN/projects/js/xdocs/sql.xml
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/apps/xmlrpc.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/apps/xmlrpc.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/apps/xmlrpc.xml
(original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/apps/xmlrpc.xml Tue Aug
30 02:10:31 2005
@@ -36,7 +36,7 @@
</section>
<section name="How it works">
<p>The client generator is roughly similar to the
- <a href="../patterns/proxy.html">Proxy Generator</a>:
+ <a href="./../patterns/proxy.html">Proxy Generator</a>:
Assuming that you have classes A, B, and C on the server,
which are being called via XML-RPC, the generator creates
classes A', B', and C' with roughly the same set of public
@@ -83,7 +83,7 @@
<p>In particular, note that the generated classes are
automatically converting from or to primitive types.
A basic implementation for the
- <a href="../apidocs/org/apache/ws/jaxme/js/apps/XmlRpcCaller.html">
+ <a href="./../apidocs/org/apache/ws/jaxme/js/apps/XmlRpcCaller.html">
XmlRpcCaller</a> would be:</p>
<source>
public class MyCaller implements org.apache.ws.jaxme.js.apps.XmlRpcCaller {
@@ -207,7 +207,7 @@
<td>One or more file sets specifying the server side classes,
for which clients are being generated. These classes may either
be specified as sources (in which case the
- <a href="../apidocs/org/apache/ws/jaxme/js/util/JavaParser.html">
+ <a href="./../apidocs/org/apache/ws/jaxme/js/util/JavaParser.html">
Java parser</a> is used for scanning them, or as compiled classes,
in which case Java reflection is being used.</td>
<td>Yes</td>
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/index.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/index.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/index.xml (original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/index.xml Tue Aug 30
02:10:31 2005
@@ -70,8 +70,8 @@
<anchor id="history"/>
<section name="History">
<p>The framework was originally part of the
- <link href="ext:jaxme1">JaxMe 1</link> generator, the predecessor of
- <link href="ext:jaxme2">JaxMe 2</link>.
+ <a hrefkey="link.jaxme1">JaxMe 1</a> generator, the predecessor of
+ <a hrefkey="link.jaxme2">JaxMe 2</a>.
It got greatly improved as part on the work of JaxMe 2.
Roughly in January 2003 it began to live a live of its own, because the
framework
was picked up for other projects. So it made sense to separate JaxMeJS
in an own
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/jparser.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/jparser.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/jparser.xml (original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/jparser.xml Tue Aug 30
02:10:31 2005
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2004 The Apache Software Foundation.
@@ -21,7 +21,7 @@
<body>
<section name="Why Source Reflection?">
<p>Java Source Generation is frequently based on reflection. For
example,
- the <a href="patterns/proxy.html">Proxy Generator</a> works
+ the <a href="./patterns/proxy.html">Proxy Generator</a> works
roughly like this: Class A is inspected using Java Reflection.
A new class B is created. For any public method in A, a method
in B is created, that invokes A.</p>
@@ -48,7 +48,7 @@
converts it into an instance of
<a href="./apidocs/org/apache/ws/jaxme/js/JavaSource.html">
JavaSource</a>. The Java parser is internally based on an
- <link href="ext:antlr">AntLR parser</link>. (AntLR is a public
+ <a hrefkey="link.antlr">AntLR parser</a>. (AntLR is a public
domain parser generator.)</p>
<p>The created
<a href="./apidocs/org/apache/ws/jaxme/js/JavaSource.html">
@@ -65,11 +65,11 @@
<section name="Using the JavaParser">
<p>To use the Java parser, your classpath must obviously contain
the file jaxmejs.jar. However, because the actual parser is
- generated by <link href="ext:antlr">AntLR</link>, you need the
+ generated by <a hrefkey="link.antlr">AntLR</a>, you need the
file antlr.jar as well. Both files come to you as part of the
JaxMe distribution. Besides, a current version of antlr.jar
(2.7.4, as of this writing) can always be obtained from
- <link href="ext:antlr">www.antlr.org</link>. However, if you
+ <a hrefkey="link.antlr">www.antlr.org</a>. However, if you
replace the AntLR parser, then you should probably use the
JaxMe source distribution, and rebuild the binaries, thus
creating a new parser.</p>
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/chains.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/chains.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/chains.xml
(original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/chains.xml Tue
Aug 30 02:10:31 2005
@@ -77,7 +77,7 @@
</source>
<p>If you take this methods as events, then you might well write a
default
class A implementing the interface. The other classes are implemented
as
- subclasses of an automatically generated <a href="proxy.html">proxy
class</a>.
+ subclasses of an automatically generated <a href="./proxy.html">proxy
class</a>.
For example, the class B might just add another method to the
<code>Foo</code>.
This might look like the following:</p>
<source>
@@ -137,7 +137,7 @@
}
</source>
<p>The proxy chain pattern is implemented by the
- <a
href="../apidocs/org/apache/ws/jaxme/js/pattern/ChainGenerator.html">ChainGenerator</a>.
+ <a
href="./../apidocs/org/apache/ws/jaxme/js/pattern/ChainGenerator.html">ChainGenerator</a>.
From within Ant, it looks like the following:</p>
<source>
<chainGenerator destDir="src">
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/proxy.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/proxy.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/proxy.xml
(original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/proxy.xml Tue
Aug 30 02:10:31 2005
@@ -35,7 +35,7 @@
the derivation of subclasses. In fact the derivation of a subclass is
much
more obvious, simple and faster than the use of an
InvocationHandler.</p>
<p>The proxy generator is implemented by the class
- <a
href="../apidocs/org/apache/ws/jaxme/js/pattern/ProxyGenerator.html">ProxyGenerator</a>.
+ <a
href="./../apidocs/org/apache/ws/jaxme/js/pattern/ProxyGenerator.html">ProxyGenerator</a>.
Use of the ProxyGenerator is demonstrated in the Ant target
"generate.proxy".</p>
<p>The proxy generator Ant task supports the following attributes:</p>
<table>
@@ -114,9 +114,9 @@
<section name="Multiple Inheritance">
<p>Multiple inheritance is a design pattern which is not so easy to
implement
in Java - unless you use the
- <a
href="../apidocs/org/apache/ws/jaxme/js/pattern/ProxyGenerator.html">ProxyGenerator</a>.
+ <a
href="./../apidocs/org/apache/ws/jaxme/js/pattern/ProxyGenerator.html">ProxyGenerator</a>.
This is demonstrated by the JUnit test
- <a
href="../apidocs/org/apache/ws/jaxme/js/junit/MultipleInheritanceTest.html">MultipleInheritanceTest</a>,
+ <a
href="./../apidocs/org/apache/ws/jaxme/js/junit/MultipleInheritanceTest.html">MultipleInheritanceTest</a>,
which creates a subclass of <code>java.util.Observable</code>, that
also inherits
from <code>java.util.ArrayList</code>. The example implements a list,
which
notifies its observers whenever the <code>add()</code> method is
invoked.</p>
Modified:
webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/versioning.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/versioning.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/versioning.xml
(original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/patterns/versioning.xml
Tue Aug 30 02:10:31 2005
@@ -92,7 +92,7 @@
in-memory rows. For example, there is a column updater that updates a
foreign keys value from an object that has already been cloned to its
clone. Column updaters are implementing the interface
- <a
href="../apidocs/org/apache/ws/jaxme/js/pattern/VersionGenerator.ColumnUpdater.html">
+ <a
href="./../apidocs/org/apache/ws/jaxme/js/pattern/VersionGenerator.ColumnUpdater.html">
VersionGenerator.ColumnUpdater</a>.</p>
<p>The main thing to understand when writing a column updater is that it
is not invoked at runtime, but as a part of the source generation
stage.
@@ -118,7 +118,7 @@
<dt>pTableInfo</dt><dd>Holds the generators view of the table being
cloned by the method <code>pMethod</code>. The most important
property
is the <code>table</code> property, which returns an instance of
- <a href="../apidocs/org/apache/ws/jaxme/sqls/Table.html">Table</a>
with the table name
+ <a href="./../apidocs/org/apache/ws/jaxme/sqls/Table.html">Table</a>
with the table name
and column list.</dd>
<dt>pConnection</dt><dd>A variable name which is holding an open
database connection in the generated source.</dd>
@@ -163,7 +163,7 @@
]]> </source>
<p>You might replace the VersionGenerator with a subclass, because the
above
code would emit logging statements using the
- <a href="../apidocs/org/apache/ws/jaxme/logging/package-summary.html">
+ <a
href="./../apidocs/org/apache/ws/jaxme/logging/package-summary.html">
org.apache.ws.jaxme.logging package</a>.
If you do not favour this, replace the methods
<code>logEntering</code>,
<code>logExiting</code>, <code>logFinest</code>,
<code>logFinestEntering</code>,
Modified: webservices/jaxme/branches/MAVEN/projects/js/xdocs/sql.xml
URL:
http://svn.apache.org/viewcvs/webservices/jaxme/branches/MAVEN/projects/js/xdocs/sql.xml?rev=264745&r1=264744&r2=264745&view=diff
==============================================================================
--- webservices/jaxme/branches/MAVEN/projects/js/xdocs/sql.xml (original)
+++ webservices/jaxme/branches/MAVEN/projects/js/xdocs/sql.xml Tue Aug 30
02:10:31 2005
@@ -50,7 +50,7 @@
System.out.println(schema.getName().toString()); // Prints myschemaname
</source>
<p>However, it is not unusual to avoid the schema. Even more, there are
- SQL databases like <link href="ext:mysql">MySQL</link> which do not
+ SQL databases like <a hrefkey="link.mysql">MySQL</a> which do not
even support a schema. In that case you simply use the so-called
default
schema. The only difference between the default schema and other
schemas
is that the former doesn't have a name.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
