lams-github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
finish export portfolio function, need further test.

    • -12
    • +0
    /lams_tool_sbmt/web/export/exportportfolio.jsp
finish export portfolio function, need further test.

    • -0
    • +5
    /lams_tool_sbmt/conf/xdoclet/servlets.xml
    • -3
    • +3
    /lams_tool_sbmt/db/sql/tool_insert.sql
    • -5
    • +15
    /lams_tool_sbmt/web/WEB-INF/web.xml
    • -0
    • +96
    /lams_tool_sbmt/web/export/exportportfolio.jsp
Setup dummy learning functionality so that learner interface can be used in the Alpha version. Supports joining a lesson.

    • binary
    /lams_build/lib/lams/lams-learning.jar
    • -0
    • +8
    /lams_learning/conf/xdoclet/taglibs.xml
    • -0
    • +48
    /lams_learning/web/WEB-INF/lams.tld
    • -13
    • +39
    /lams_learning/web/controlBottomFrame.jsp
    • -1
    • +60
    /lams_learning/web/controlTopFrame.jsp
  1. … 4 more files in changeset.
*** empty log message ***

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.

    • binary
    /lams_build/lib/lams/lams-monitoring.jar
    • -141
    • +46
    /lams_monitoring/web/dummy.jsp
    • -0
    • +42
    /lams_monitoring/web/dummyControlFrame.jsp
    • -0
    • +114
    /lams_monitoring/web/dummyDetail.jsp
    • -0
    • +73
    /lams_monitoring/web/dummyStart.jsp
    • -0
    • +26
    /lams_monitoring/web/dummyStarted.jsp
    • -0
    • +47
    /lams_monitoring/web/welcome.jsp
Fix session table key bug

    • -1
    • +7
    /lams_tool_sbmt/db/sql/create_lams_tool_sbmt.sql
    • -1
    • +1
    /lams_tool_sbmt/db/sql/table-schema.sql
Fix SQL bug for message by session id query.

just added some comments

changes to the export functionalities

    • binary
    /lams_build/lib/lams/lams-learning.jar
some changes to AbstractExportPortfolioServlet and HttpUrlConnectionUtil

removed the try catch statement that was wrapped around writeResponseToFile exceptions arent thrown now...instead a file is generated

updated to use new getOrderedActivityList(LearnerProgress)

renaming of Portfolio and ToolPortfolio objects

modified it so that if it detects that the array of ToolPortfolios is null, it will just generate a main page stating that the portfolio export is not supported

major change is replacing the previously known Portfolio objects to be ToolPortfolio objects exportPortfolioFor* methods now return a Portfolio object, which contains the array of ToolPortfolio objects. the member variable exportTmpDir is removed and placed in the Portfolio object instead.

In most cases, instead of throwing exceptions, an error message is written to a file, however the real error is logged.

updated some comments. changed getOrderedActivityList(Long learnerProgressId) to getOrderedActivityList(LearnerProgress learnerProgress) for some reason the failed to lazily initialize exception doesnt occur anymore

Previously known as the Portfolio object

A portfolio object, now holds the attribute exportTmpDir - the temporary directory in which this export will place its files. and it contains an array of ToolPortfolio objects. ToolPortfolio was previously known as a Portfolio object, now renamed to ToolPortfolio

*** empty log message ***

instead of throwing exceptions, it will just create a main page sayin gthat the tool activity does not support portfolio export

when trying to connect to a tools export url, instead of throwing exception a status 200 isnt received, it will return null so that the export service can generate a file saying that an error has occurred.

*** empty log message ***

    • -0
    • +0
    /lams_tool_lamc/testCommit.txt
*** empty log message ***

    • -22
    • +15
    /lams_tool_lamc/build.properties
*** empty log message ***

    • -0
    • +121
    /lams_tool_lamc/db/sql/create_lams_tool_mc.sql
    • -0
    • +16
    /lams_tool_lamc/db/sql/drop_lams_tool_mc.sql
    • -0
    • +0
    /lams_tool_lamc/db/sql/insert_lams_tool_mc.sql
Testing whether I can check into the mcq project. No real change.

Updated tool-deploy to suit xml format for deploy properties file.

Rolling back mc changes that were accidently made to qa

    • -1
    • +1
    /lams_tool_laqa/conf/jar/META-INF/MANIFEST.MF
    • -1
    • +1
    /lams_tool_laqa/conf/war/META-INF/MANIFEST.MF
    • -820
    • +0
    /lams_tool_laqa/db/model/lams_tool_mc.clay
    • -0
    • +561
    /lams_tool_laqa/db/model/lams_tool_qa.clay
    • -3
    • +3
    /lams_tool_laqa/db/sql/activity_insert.sql
    • -121
    • +0
    /lams_tool_laqa/db/sql/create_lams_tool_lamc.sql
  1. … 96 more files in changeset.
Add comment

*** empty log message ***

Added dummy learner page

    • -0
    • +16
    /lams_central/web/learner.jsp