lams-github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
updated the jsp for activeModule

updated the jsp for constant constant activeModule

updated the starter for constant ACTIVE_MODULE

updated public ActionForward editActivityQuestions(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException, ToolException

no changes

added a logger.debug()

added FlushMode.AUTO

added contant DEFINE_LATER_EDIT_ACTIVITY

new insert test data target

added test.contentid

changed the urls (removed the starter path)

*** empty log message ***

most testcases now run except the ones that try to getDefaultContentId by Tool signature

fixed up tests cases so they now can run fixed tearDown method

made some private declarations protected so it can be used by other test classes

removeToolContent - it will try to delete files from repository before deleting the NoticeboardContent object.

createToolSession - modifications made as to way its saved

changed the deletion methods to use createQuery instead of getHibernateTemplate.delete()

removed the get*UID method and remove*UID methods as they arent used

inserts test data to run nb not required for junit tests tho

    • -0
    • +25
    /lams_tool_nb/db/sql/insert_test_data.sql
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.

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.

    • binary
    /lams_build/lib/lams/lams-monitoring.jar
LDEV-67: Run sequences were not going in the correct workspace folder. Added a default runtime sequence folder to the workspace object.

monitoring screen allows the download of instruction files.

files removed.NbAuthoringStarterAction ->code now lies in unspecified method of AuthoringAction class NbMonitoringStarterAction -> code now lies in unspecified method of MonitoringAction class.

the unspecified method contains the code that used to be in NbMonitoringStarterAction class, sets up the monitoring environment

removed NbMonitoringStarterAction and so changed the monitoring url

update XML read file.

updated tags-fck-editor and lams tags

    • -1
    • +2
    /lams_tool_lamc/web/SystemErrorContent.jsp
moved this under learning/

    • -74
    • +0
    /lams_tool_lamc/web/RedoQuestions.jsp
added test urls for copy tool content, remove tool content and define later