[jboss-remoting-commits] JBoss Remoting SVN: r4613 - remoting3/trunk/api/src/main/java/org/jboss/remoting.
jboss-remoting-commits at lists.jboss.org
jboss-remoting-commits at lists.jboss.org
Wed Oct 22 20:14:24 EDT 2008
Author: david.lloyd at jboss.com
Date: 2008-10-22 20:14:24 -0400 (Wed, 22 Oct 2008)
New Revision: 4613
Modified:
remoting3/trunk/api/src/main/java/org/jboss/remoting/Client.java
Log:
small clarification (javadoc)
Modified: remoting3/trunk/api/src/main/java/org/jboss/remoting/Client.java
===================================================================
--- remoting3/trunk/api/src/main/java/org/jboss/remoting/Client.java 2008-10-23 00:12:05 UTC (rev 4612)
+++ remoting3/trunk/api/src/main/java/org/jboss/remoting/Client.java 2008-10-23 00:14:24 UTC (rev 4613)
@@ -35,7 +35,7 @@
* locally, a {@code ReplyException} is thrown. In this case the operation is known to have completed without error
* but the actual detailed reply cannot be known. In cases where the reply would be ignored anyway, this exception
* type may be safely ignored (possibly logging it for informational purposes). This exception is typically caused
- * by an {@code ObjectStreamException} thrown while marshalling the reply, though other causes are also possible.
+ * by an {@code ObjectStreamException} thrown while unmarshalling the reply, though other causes are also possible.
* <p/>
* If the result of the operation is known to be impossible to ascertain, then an {@code IndeterminateOutcomeException}
* is thrown. Possible causes of this condition include (but are not limited to) the connection to the remote side
More information about the jboss-remoting-commits
mailing list