hammant 2003/01/07 15:27:26
Modified: altrmi/src/xdocs client-usage.xml connection-listeners.xml
index.xml pingers.xml
Log:
renames in docs.
Revision Changes Path
1.3 +4 -4 jakarta-avalon-excalibur/altrmi/src/xdocs/client-usage.xml
Index: client-usage.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/client-usage.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- client-usage.xml 26 Jul 2002 16:21:36 -0000 1.2
+++ client-usage.xml 7 Jan 2003 23:27:25 -0000 1.3
@@ -24,7 +24,7 @@
env.put(
Context.INITIAL_CONTEXT_FACTORY,
"org.apache.excalibur.altrmi.client.impl.naming.DefaultAltrmiInitialContextFactory");
-env.put(Context.PROVIDER_URL, "altrmi://localhost:1235/SocketCustomStream");
+env.put(Context.PROVIDER_URL, "altrmi://somehost:1235/SocketCustomStream");
Context ctx = new InitialContext(env);
TestInterface ti = (TestInterface) ctx.lookup("Hello");
]]>
@@ -36,8 +36,8 @@
Directly using AltRMI classes, you can lookup the same interface.
<source>
<![CDATA[
-AltrmiFactory af = new ClientClassAltrmiFactory(false);
-af.setHostContext(new SocketCustomStreamHostContext("127.0.0.1", 1235));
+Factory factory = new ClientClassAltrmiFactory(false);
+factory.setHostContext(new SocketCustomStreamHostContext("somehost", 1235));
TestInterface ti = (TestInterface) af.lookup("Hello");
]]>
</source>
1.4 +2 -2
jakarta-avalon-excalibur/altrmi/src/xdocs/connection-listeners.xml
Index: connection-listeners.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/connection-listeners.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- connection-listeners.xml 12 Dec 2002 07:56:59 -0000 1.3
+++ connection-listeners.xml 7 Jan 2003 23:27:26 -0000 1.4
@@ -26,7 +26,7 @@
<p>
This listener does not log method calls and tries ten times to
reconnect the the abended service in the case of failure. After that
- it throws an AltrmiInvocationException. In the case of suspension
+ it throws an InvocationException. In the case of suspension
it honours the suggestion of the server to wait n seconds before
trying again.
</p>
1.9 +10 -15 jakarta-avalon-excalibur/altrmi/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/index.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- index.xml 27 Dec 2002 00:07:27 -0000 1.8
+++ index.xml 7 Jan 2003 23:27:26 -0000 1.9
@@ -45,12 +45,12 @@
The principal benefit for a developer making beans or an application server
is
that RemoteException is missing. That does not mean that communications
failure
is ignored. AltRMI still illustrates communication failure via
- AltrmiInvocationException which a subclass of RuntimeException. This
basically
+ InvocationException which a subclass of RuntimeException. This basically
allows the exception to be thrown, but not specified on each method (like
RemoteException does). Many feel that allowing the bean developer to
ignore the robustness issues is a mistake. We think not given the following.
<ol>
- <li>The container could be programmed to know about
AltrmiInvocationException.</li>
+ <li>The container could be programmed to know about InvocationException.</li>
<li>AltRMI has configurable policies that can help re-establish connection
whilst in use.</li>
<li>Standard handling of RemoteException sucks.</li>
<li>It is difficult in EJB, in terms of coverage, to test your huge amounts
of
@@ -59,7 +59,7 @@
exceptions are already caught.</li>
</ol>
</p>
- <s2 title="1. The container could be programmed to know about
AltrmiInvocationException">
+ <s2 title="1. The container could be programmed to know about
InvocationException">
<p>
A lot of beans coding is 'bean invokes method in bean which invokes
method in bean'. In
this case there are several places in the invocation stack where the
container's logic
@@ -123,7 +123,7 @@
<p>
Webapps that use multiple beans (assuming a decent MVC separation or a
framework like
Velocity) already have a place where central exception handling is going
on. With
- AltRMI, you can catch AltrmiInvocationException where you feel is fit.
EJB teams that
+ AltRMI, you can catch InvocationException where you feel is fit. EJB
teams that
choose to have throws RemoteException on all methods (percolating it up
the stack) probably
also choose to finally handle it centrally. Like so ...
</p>
@@ -139,7 +139,7 @@
templateName = processRequest(req, resp, ctx);
// Get the template
template = getTemplate(templateName);
- } catch (AltrmiInvocationException aie) {
+ } catch (InvocationException aie) {
template = getTemplate("commfailure.vm");
}
} catch (ResourceNotFoundException rnfe) {
@@ -182,20 +182,15 @@
</s2>
</s1>
<s1 title="External uses of AltRMI">
- <s2 title="Transport package in Avalon-Cornerstone">
+ <s2 title="Instrument project - Avalon">
<p>
- Allowing transparent publication of phoenix services and for phoenix
services. See
- <link
href="http://jakarta.apache.org/avalon/cornerstone";>Cornerstone</link>.
- </p>
- <p>
- Using that transport package are <link
href="http://jakarta.apache.org/avalon/apps/apps/db";>
- AvalonDB</link> and <link
href="http://jakarta.apache.org/avalon/apps/apps/demo";>Demos</link>
- (both in Avalon-Apps).
+ The Excalibur <link
href="http://jakarta.apache.org/avalon/excalibur/instrument/";>
+ Instrument</link> package as part of Avalon.
</p>
</s2>
<s2 title="Enterprise Object Broker">
<p>
- An EJB replacement, current hosted at <link
href="http://eob.sourceforge.net";>
+ An EJB replacement, current hosted at <link
href="http://www.enterpriseobjectbroker.org";>
SourceForge</link>
</p>
</s2>
1.5 +2 -2 jakarta-avalon-excalibur/altrmi/src/xdocs/pingers.xml
Index: pingers.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/pingers.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- pingers.xml 12 Dec 2002 07:56:59 -0000 1.4
+++ pingers.xml 7 Jan 2003 23:27:26 -0000 1.5
@@ -19,7 +19,7 @@
<p>
It is possible to write your own or extend the exiting
ones if there are different requirements. The interface for bespoke
pingers
- is <link
href="api/org/apache/excalibur/altrmi/client/AltrmiConnectionPinger.z@z">here</link>
+ is <link
href="api/org/apache/excalibur/altrmi/client/ConnectionPinger.html">here</link>
</p>
</s1>
<s1 title="Pinger types">
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
