lams-github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-4696 Make all @ManyToOne and @OneToOne lazy

Hibernate 3 used lazy loading of single-object relationships by default.

JPA's default setting is eager. When loading entities all references are

loaded immediately using JOINs. A large entity, like Learning Design,

can have a query consisting of 25 JOINs. It makes it very slow.

There is no way to change JPA's default behaviour. In order to make JPA

annotations behave like old Hibernate, each of them got an explicit

attribute saying that loading is lazy.

  1. … 156 more files in changeset.
LDEV-4391 Fix column mapping

LDEV-4391 Fix column mapping

LDEV-4391 Show export LD label in authoring.

It seems that with new jQuery show() method does work if DOM node is not

attached to an document (yet). For example if a piece of HTML gets

cloned with jQuery and it is not appended to any parent, show() will not

work.

Merge branch 'lams31' into LDEV-4391

LDEV-4713 Allow initialisation of a field with NULL value

Merge branch 'lams31' into LDEV-4391

Merge branch 'LDEV-4713' into lams31

LDEV-4713 Fix ordering of conditions in Survey

LDEV-4713 Allow initialisation of a field with NULL value

LDEV-4696 Delete obsolete Hibernate .hbm.xml files

Merge branch 'LDEV-4712' into lams31

LDEV-4712, LDEV-4644 Fix a query used for fetching outcomes

LDEV-3115 Fix detection of old LD being converted into new format.

If X and Y were 0, detection did not work.

Merge branch 'lams31' into LDEV-4391

LDEV-4696 Proper use of @MapsId with @EmbeddableId

LDEV-4391 Fix properties dialog in authoring

When content was added to modal dialog, it was still hidden. We had to

explicitly show it in JS.

LDEV-4391 Upgrade Boostrap to 3.3.7

Previous version did not support jQuery 3.

    • -3
    • +4
    /lams_central/web/css/bootstrap.min.css
LDEV-4391 Get rid of redundant jQuery UI themes

Only bootstrap theme is used now.

    • -1
    • +1
    /lams_admin/web/cleanupPreviewLessons.jsp
    • -1
    • +1
    /lams_admin/web/import/importGroups.jsp
    • -1
    • +1
    /lams_admin/web/import/importexcel.jsp
    • -1
    • +1
    /lams_admin/web/import/importresult.jsp
    • -1
    • +1
    /lams_admin/web/lti/ltiConsumerList.jsp
  1. … 83 more files in changeset.
LDEV-4391 Upgrade jQuery UI to 1.12.1

    • -11
    • +11
    /lams_central/web/includes/javascript/jquery-ui.js
LDEV-4391 Upgrade timepicker script to 1.6.3

LDEV-4391 Upgrade tablesorter script to 2.31.1

    • -48
    • +1
    /lams_central/web/css/jquery.tablesorter.pager.css
    • -222
    • +1
    /lams_central/web/css/jquery.tablesorter.theme-blue.css
    • -167
    • +1
    /lams_central/web/css/jquery.tablesorter.theme.bootstrap.css
LDEV-4391 Update jQuery to version 3.3.1. Add Migration Plugin.

jQuery was upgraded to version 3.3.1.

It was put into jquery.js file which is referenced by LAMS JSPs.

In the same file below jQuery code Migration Plugin 3.0.0 was pasted.

This way it gets loaded every time jQuery gets loaded without extra HTML

tags.

The Migration Plugin reintroduces API removed from jQuery 3.

This way we can benefit from jQuery 3 efficiency and security and do not

have to use everywhere its new API straight away.

jQuery and Migration Plugin in jquery.js are in their compressed,

production version.

The Plugin produces only debug information in JS console: "JQMIGRATE:

Migrate is installed, version 3.0.0". It appears every time the Plugin

gets loaded. We can silence this message if we want to.

In jquery.migration.js the two above scripts come in their development

version.

The Plugin produces warnings every time deprecated API is used, pointing

to spots which require rewriting to comply with jQuery 3 new API.

While production jQuery + Plugin solution seems to work fine, we should

ultimately aim at rewriting our code and sticking to pure jQuery 3.

During development jquery.migration.js contents should be copied to

jquery.js to enable warnings.

Clean www dirs otherwise builds from other branches causes problems.

www does not have the build directories cleaned when the Java code is

built so they need to be cleaned explicitly otherwise files that are

left in the build area from another branch are deployed.

Merge branch 'LDEV-4704' into lams31

LDEV-4669 Switch to using placeholder attribute

Also stop copying tags to lams_tool_bbb

    • -6
    • +7
    /lams_admin/web/WEB-INF/tags/Rating.tag
    • -6
    • +7
    /lams_central/web/WEB-INF/tags/Rating.tag
  1. … 19 more files in changeset.
LDEV-4704 Slimming for WildFly standalone mode

Multiple sections from configuration file have been removed.

Multiple unused libraries have been removed.

    • -0
    • +449
    /lams_build/conf/slim/standalone.xml
LDEV-4704 Clean up commented out dependencies

LDEV-4702 Leaders changed answers appear on refresh

LDEV-4707 Remove never used fields from TaskListItem