Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-40036

Unable to configure sitestats properties with key@component=value syntax

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 12.5, 19.0
    • Fix Version/s: None
    • Component/s: Sitestats
    • Labels:
      None
    • Test Plan:
      Hide

      To reproduce:

      Take a sakai.property line from Sakai 11, like "collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager=false" and use it as is in master. It will not change the value.

       

      Show
      To reproduce: Take a sakai.property line from Sakai 11, like "collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager=false" and use it as is in master. It will not change the value.  

      Description

      I think this is related to some post-Sakai-11 spring/hibernate upgrade, but I'm now unable to use configuration like

      collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager=false

      Instead, I discovered I have to use

      collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager.target=false

      because it appears the bean id has changed to "org.sakaiproject.sitestats.api.StatsUpdateManager.target" and "org.sakaiproject.sitestats.api.StatsUpdateManager" is now the id for the transaction proxy.

      Is this naming change required, or can we just change it back to keep things simple for people managing sakai.properties?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                plukasew Paul Lukasewych
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Git Source Code