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.
This commit is contained in:
parent
cea36ffc47
commit
17df399f68
@ -114,7 +114,12 @@ public class TestChatClient extends JFrame {
|
|||||||
}
|
}
|
||||||
|
|
||||||
public static void main(String... args) throws Exception {
|
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
|
// Grab a host string from the user
|
||||||
String s = getString(null, "Host Info", "Enter chat host:", "localhost");
|
String s = getString(null, "Host Info", "Enter chat host:", "localhost");
|
||||||
|
Loading…
x
Reference in New Issue
Block a user