Re: Cluster API status

2013-02-03 Thread seba.wag...@gmail.com
+++ 3) The attribute pass in the Server Entity must be FetchType.Lazy and the insert/update method in the UI/ServerDao must be so modified that the Server's Entity password is only changed when explicitly set. Otherwise we would need to create a ServerDTO and use that everywhere where a Server

Re: Cluster API status

2013-02-03 Thread Maxim Solodovnik
What about the chat, I have seen you made some changes to the chat lately Maxim? Is the Chat in the dashboard now in the database? I add chat to the DB for Wicket only (only global chat for now with small amount of testing) I had no plans to change it for Flash app On Mon, Feb 4, 2013 at

Re: Cluster API status

2013-02-03 Thread seba.wag...@gmail.com
ok thx, I guess we can also let the dashboard chat untouched. Theoretically there is no need to put it into the database as long as the clients initially always connect to the same node (as we did plan). But the chat history in the conference room needs to be put into the db as it could

RE: Cluster API status

2013-02-03 Thread Irina Arkhipets
regards, Irina. -Original Message- From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Monday, February 04, 2013 11:01 AM To: dev Subject: Re: Cluster API status I would vote to have the backups tested. We will dis-attract a lot of people if their backups won't import from old