Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-67876

Configuration objects should never be created with null for the location. This allows forces the configuration objects to be bound to a bundle and not accessible from other bundles.

    Details

      Description

      Binding configurations to a specific location will lead to errors like:

      11:37:49,575 ERROR [CM Configuration Updater (Update: pid=com.liferay.portal.security.sso.token.configuration.TokenConfiguration)][org_apache_felix_configadmin:97] Cannot use configuration com.liferay.portal.security.sso.token.configuration.TokenConfiguration for [org.osgi.service.cm.ManagedService, id=2577, bundle=226//com.liferay.portal.configuration.settings-2.0.2.jar]: No visibility to configuration bound to /com.liferay.portal.security.sso.token-3.0.1.jar

      {org.osgi.service.cm.ConfigurationAdmin}

      =

      {service.vendor=Apache Software Foundation, service.pid=org.apache.felix.cm.ConfigurationAdmin, service.description=Configuration Admin Service Specification 1.2 Implementation, service.id=53, service.bundleid=27, service.scope=bundle}

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  2 years, 24 weeks, 5 days ago

                  Packages

                  Version Package
                  7.0.0 DXP FP3
                  7.0.X EE
                  7.1.X
                  Master