From f3f1e1f73c8070de77b56f6e4d3fcb77f10795d7 Mon Sep 17 00:00:00 2001
From: Martin Oberhuber < martin.oberhuber@windriver.com>
Date: Tue, 15 Sep 2009 20:48:29 +0000
Subject: [PATCH] [cleanup] Improve user message for network IO problem

---
 .../clientserver/messages/SystemNetworkIOException.java    | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/rse/plugins/org.eclipse.rse.services/clientserver/org/eclipse/rse/services/clientserver/messages/SystemNetworkIOException.java b/rse/plugins/org.eclipse.rse.services/clientserver/org/eclipse/rse/services/clientserver/messages/SystemNetworkIOException.java
index 005d89253cb..5ff5c5f49d6 100644
--- a/rse/plugins/org.eclipse.rse.services/clientserver/org/eclipse/rse/services/clientserver/messages/SystemNetworkIOException.java
+++ b/rse/plugins/org.eclipse.rse.services/clientserver/org/eclipse/rse/services/clientserver/messages/SystemNetworkIOException.java
@@ -55,6 +55,13 @@ public class SystemNetworkIOException extends SystemRemoteMessageException {
 		String message = remoteException.getMessage();
 		if (message == null) {
 			message = remoteException.getClass().getName();
+		} else {
+			// TODO Most remote messages like IOException don't have a message
+			// that's understandable without the class type. For full translated
+			// messages, code like in the Eclipse Team/CVS provider would need
+			// to translate into readable messages. See also
+			// o.e.tm.terminal.ssh/SshMessages#getMessageFor(Throwable).
+			message = remoteException.getClass().getName() + ": " + message; //$NON-NLS-1$
 		}
 		String msgTxt = NLS.bind(CommonMessages.MSG_COMM_NETWORK_ERROR, message);