48 | | * The implementations of the facade interfaces are in the org.sophie2.server.facade.impl package. |
49 | | * The !UserManager implementation - the !ServerUserManager works with !ServerSession and provides access to logged user with the help of a string - session id. |
50 | | * The !ServerSession class represents the Sophie 2 Server session and keeps the relations sessionId -> logged in user. Also it takes care of the session timeouts. |
51 | | * Second the mock server must be refactored to use the new facade model. For now only it's three methods for login, retrieving groups and checking existence of a user are necessary to be implemented (see [wiki:S2S_CORE_MOCK_SERVER_R0]). Also the test cases must be refactored. The new mock facade is shown in the class diagram. |
52 | | * The third step is to refactor the web services layer. For now there is only one web service - the user web service (see [wiki:S2S_WEB_SERVICES_R0]). It must use the !ServerSession and it's session IDs for managing the users. |
53 | | * The fourth step is to refactor the current web to use the facade instead the core logic. |
| 48 | * The server side's implementations of the facade interfaces are in the org.sophie2.server.facade.impl package. |
| 49 | * The !UserManager implementation - the !ServerUserManager uses the !ServerSession and provides access to logged user with the help of a string - session id. |
| 50 | * The !ServerSession class represents the Sophie 2 Server session and keeps the relations sessionId -> logged-in user. Also it takes care of the session timeouts. |
| 51 | * Second the mock server must be refactored to use the new facade model. For now only its three methods for login, retrieving groups and checking existence of a user are necessary to be implemented (see [wiki:S2S_CORE_MOCK_SERVER_R0]). Also the test cases must be refactored. The new mock facade is shown in the class diagram. |
| 52 | * The third step is to refactor the web services layer. For now there is only one web service - the !UserWebService (see [wiki:S2S_WEB_SERVICES_R0]). It must use the !ServerSession and it's session IDs for managing the users. |
| 53 | * The fourth step is to refactor the security part of the current web to use the facade instead the core logic. |