Details

      Description

      A lot of weird bugs come from the Expando API when it is not called from a regular portal thread (ie spawn a thread that does a job that has Expando in it) because it relies on CompanyThreadLocal.getCompanyId to namespace the tables, columns, rows, and values.

      Modified the API to add company id explicitly.

      A temporary workaround is to set the CompanyThreadLocal before calling an Expando API and then resetting it.

      Deprecated a few of the very often used API calls to not take in a company id (default to the old way), but this will be removed in the future as it is inherently unsafe.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                support-lep@liferay.com SE Support
                Reporter:
                brian.chan Brian Chan
                Participants of an Issue:
                Recent user:
                Esther Sanz
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  7 years, 42 weeks, 4 days ago