...
Thus, the developer can code and debug all in Java by working depending to his needs in the backend project or in the client project.
Code Structure | |
|---|---|
Frontend project | Backend project |
GWT code | Sakai's tool code |
client | API |
public | Impl |
shared | Tool |
- One project for the backend part
OpenSyllabus backend is organized as a classical Sakai's tool following a File Structure based on classic Sakai's tool directories, such as : API, Implementation and Tool directory.
- API
- Impl
- Tool
But in the Tool directory there is something new : the compiled GWT content (all the generated GWT stuff : pure JavaScript and HTML).
There are also RPCServlets and RPCInterfaces for Remote Procedure Call exchanges.
Code Structure | |
|---|---|
Frontend project | Backend project |
GWT code | Sakai's tool code |
client | API |
public | Impl |
shared | Tool |