Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add finishLessonOnSchedule interface

  1. … 1 more file in changeset.
Add finishLessonOnSchedule interface

Add scheduled lesson start job.

Working on createLesson and initializeLesson

    • -0
    • +32
    ./org/lamsfoundation/lams/monitoring/MonitoringConstants.java
  1. … 4 more files in changeset.
add startLesson message

  1. … 1 more file in changeset.
LDEV-79: Added remove lesson feature to the dummy monitoring interface.

  1. … 2 more files in changeset.
Improved some of the comments

Add DISABLE_LESSON to lesson class

removeLesson

  1. … 1 more file in changeset.
arhieve lesson : send WDDX package to flash client

  1. … 1 more file in changeset.
Corrected comment.

LDEV-61 Fixing tool sessions - all users were getting separate tool sessions. Modified monitoring service to suit changes to ToolActivity.createToolSessionForActivity()

LDEV-67: Run sequences were not going in the correct workspace folder. Now when the lesson starts, the learning design is placed in the default runtime sequence folder. If such a folder does not exist, the learning design is placed in the original folder. Also changed lams.jar to add a default runtime sequence folder to the workspace object.

Also cleaned up MonitoringService - removed a few member variables and methods that are no longer used, and removed the matching entries from the context file.

  1. … 1 more file in changeset.
Modified the dummy monitoring screen to support the new Activity.getAuthoringActivityDTOSet() method.

  1. … 1 more file in changeset.
Fixed display of the parallel activities on the dummy monitoring screen. Previously it was using the activities from in the learning design and the parallel activity was a CGLIB entry, which didn't give access to the activities method. Added a new session parameter, activities, which contains a set of AuthoringActivityDTO objects and these are used in the place of the learning design.

  1. … 2 more files in changeset.
The rule to work out whether to pre-initialise the tool session was wrong. Was initialising for grouped activities, we want to initialise the non-grouped activities.

  1. … 1 more file in changeset.
Added archive a lesson feature

  1. … 2 more files in changeset.
Regigged the dummy monitoring screen. Made the layout more compact, moved the learner functionality to the learner screens.

Fixed a transaction bug with startLesson - the method was not named consistently in the applicationContext file, so the method was not part of a proper transaction. As such, the db changes done by the method were lost. This resulted in the lesson staying in the created state, never going onto the started state. Made the naming consistent and it now goes into the started state as expected.

  1. … 10 more files in changeset.
Fixed the url processing to remove the escaping from & in wddx'd urls

Updated web.xml to include the context files for all the "current" deployed tools. Added matching tool jars to classpath. Stopped deploying the classes to WEB-INF/classes Implemented more calls on the dummy monitoring page to access the learner pages.

  1. … 14 more files in changeset.
Added monitoring calls to the dummy monitoring page.

  1. … 1 more file in changeset.
Added a dummy monitoring page that will allow developers to access their tools via the normal learner url.

    • -0
    • +85
    ./org/lamsfoundation/lams/monitoring/web/DummyForm.java
    • -0
    • +294
    ./org/lamsfoundation/lams/monitoring/web/DummyMonitoringAction.java
  1. … 8 more files in changeset.
More changes to suit Hibernate 3

  1. … 32 more files in changeset.
Upgraded Hibernate to 3.0

  1. … 57 more files in changeset.
Removed ISOLATION_READ_COMMITTED from the transactions as it is not supported by the JTA transaction manager. We will have to rely on the database settings.

  1. … 7 more files in changeset.
Updated to use the new tool exceptions

  1. … 1 more file in changeset.
in checkGateStatus() - if the gate is a schedule gate, teh wddx packet will also return the gate start times and gate end times

inside checkGateStatus, added additional fields activityTypeID, and changed field name from waitingLearners to learnersWaiting

Struts dispatch actions for checkGateStatus and releaseGate, see Monitoring.doc under lams_documents for more info

implemented checkGateStatus which returns a wddx packet with certain information, however may be changed later when requirements are more clear. releaseGate returns a boolean, true to acknowledge the gate is open and false if the gate isnt opened. helper method createGateStatusInfo used in checkGateStatus()