浏览代码

Unwinding a bit of the Message vs. Message conundrum
to give new API users a proper extension point for their
own messages.


git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7069 75d07b2b-3a1a-0410-a2c5-0572b91ccdca

PSp..om 14 年之前
父节点
当前提交
0fecd032df
共有 1 个文件被更改,包括 4 次插入1 次删除
  1. 4 1
      engine/src/networking/com/jme3/network/message/Message.java

+ 4 - 1
engine/src/networking/com/jme3/network/message/Message.java

@@ -42,9 +42,12 @@ import com.jme3.network.serializing.Serializable;
  *  provide objects with common fields to the other side.
  *
  * @author Lars Wesselius
+ * @deprecated Message implementations should extend {@linke com.jme3.network.AbstractMessage} 
+ *             instead or use the {@linke com.jme3.network.Message} for referencing. 
  */
+@Deprecated
 @Serializable()
-public class Message implements com.jme3.network.Message {
+public class Message extends com.jme3.network.AbstractMessage {
     // The connector this message is meant for.
     private transient Client        connector;
     private transient Connection    connection;