| 12 | | ^(List the necessary requirements that the task must fulfill.)^ |
| | 12 | * Code requirements: |
| | 13 | * Create palette for listing server resources, make it work synchronously with the existing connections palette. |
| | 14 | * Add interface for resource part of the facade, since it currently has only user and group interfaces. This facade functionality will need 2 imlpementations : server-side and client-side. The client side will be used by the palette, the server one will provide resource access to the web services and the web UI. |
| | 15 | * Decompose the server in appropriate modules, at least having separate persistence and core. See the implementation idea for this. Refactoring will be needed. |
| | 16 | * For this revision, it would be better to fake the persistence module - everything will be persisted in the memory. This way, implementation will be easier and module dependency will be minimal. |
| | 17 | * The S2S core module must work with real Sophie2 resources, users and groups must be also resources (users and groups are part of another task, but they must be integrated in the new structure anyway). S2S core should not be directly accessible from the web ui, web services ot from the client. Only the facade will be able to do this. |
| | 18 | * Facade will expose the core functionality to the WS, DC and Web UI. It will have direct access only to the core. |
| | 19 | * S2S core should have the ability to work with custom Sophie2 resources, the facade should provide these methods to the other modules. The web services must be able to serialize the resources in order to pass them to the client. |
