From 17df399f68bd6cc7586a1550ddc8073102933fbf Mon Sep 17 00:00:00 2001 From: Paul Speed Date: Sun, 15 Nov 2015 02:13:58 -0500 Subject: [PATCH] Commented out the message class serialization and left a comment as to why: in 3.1 there is a default service that automatically does this on clients. --- .../src/main/java/jme3test/network/TestChatClient.java | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/jme3-examples/src/main/java/jme3test/network/TestChatClient.java b/jme3-examples/src/main/java/jme3test/network/TestChatClient.java index e8af4329a..a36853913 100644 --- a/jme3-examples/src/main/java/jme3test/network/TestChatClient.java +++ b/jme3-examples/src/main/java/jme3test/network/TestChatClient.java @@ -114,7 +114,12 @@ public class TestChatClient extends JFrame { } public static void main(String... args) throws Exception { - TestChatServer.initializeClasses(); + + // Note: in JME 3.1 this is generally unnecessary as the server will + // send a message with all server-registered classes. + // TestChatServer.initializeClasses(); + // Leaving the call commented out to be illustrative regarding the + // common old pattern. // Grab a host string from the user String s = getString(null, "Host Info", "Enter chat host:", "localhost");