Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

OpenSyllabus backend is organized as a classical Sakai's tool following a File Structure based on classic Sakai's tool directories, such as : API (interfaces), Impl (implementations) and Tool (webapp) directory. In the Tool directory, there are RPCServlets and RPCInterfaces for Remote Procedure Call exchanges in the src/Java folder. In addition, the Tool directory contains the Index.jsp and something new : the compiled GWT content (all the generated GWT stuff : pure JavaScript and HTML)in the src/webapp folder.

  • Code Structure
    • Frontend project (GWT code) /org/sakaiquebec/opensyllabus/
      • client
      • public
      • shared
    • Backend project (Sakai's tool code) /
      • API dir
      • Impl dir
      • Tool dir
        • Java
          • RPC Servlets
          • RPC Interfacesclient
            • rpc
              • OsylEditorGwtService.java (RPC Servlet)
              • OsylEditorGwtServiceAsync.java (RPC Async Interface)
            • server
              • OsylBackingBean.java
              • OsylEditorGwtServiceImpl.java
        • webap
          • index.jsp
          • org.sakaiquebec.opensyllabus.OsylEditorEntryPoint (JS code + HTML + images)
          • osylcoconfigs (configuration files) I18N properties files, skin: images & css, rules.xml)

Development Cycle

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.

...