#2 Server :: ServerOrderID is not being sent after a NEW_ORDER

[João Paulo Ferreira Pires]

Detail
1. When an order is created from GUI, it 's sent to the server using the Networking component, as we can see, for instance, on the log information, but the Server component is not sending an order to the client with information about ServerOrderID, because no messages of type ClientSideMessageImpl are being sent to client.

1.1 Log information:
ServerComm >> Processing ServerSideMessage: [Type: NEW_ORDER] [Nickname: wegneto] [Order: buy teste, 10 units at 10.0 EUR/unit (nickname: wegneto, serverID: 0)]

ServerComm >> Processing ServerSideMessage: [Type: NEW_ORDER] [Nickname: wegneto] [Order: buy teste 2, 50 units at 55.0 EUR/unit (nickname: wegneto, serverID: 0)]

ServerComm >> Processing ServerSideMessage: [Type: NEW_ORDER] [Nickname: wegneto] [Order: buy teste3, 1 units at 1.0 EUR/unit (nickname: wegneto, serverID: 0)]

ServerComm >> Processing ServerSideMessage: [Type: NEW_ORDER] [Nickname: alice] [Order: buy abc, 1 units at 1.0 EUR/unit (nickname: alice, serverID: 0)]

1. Based on a existing code, when a new order is received, the following code flow is executed:
   2.1 MTServer.interpretMessage(...)
   2.2 readOrder(...)

And we've validated that in the method readOrder(...), no client message is created to inform all connected clients about the new order, including the client that has created it.

1. We thing this issue is related to the defect that was identified in the Client component, described in the ticket https://sourceforge.net/p/es1-2016-metipl-90/tickets/3/, because at client side, they are waiting for a message with an ID to created orders.