Description of problem: Services Management portlet won't work in a custom portal container. It will show the error "No service's available or you don't have enough permission" in a Javascript alert. How reproducible: Easy to reproduce using quickstarts Steps to Reproduce: 1. Deploy the sample-portal container in JPP 6.0 2. Access the new container and log in as root 3. Access the Service Management gadget in URI /g/:platform:administrators/administration/servicesManagement Actual results: An alert with message "No service's available or you don't have enough permission" is shown. Expected results: List the services. Additional info: Notice that the AJAX call is done to the portal URL. See that the services management script [1] only uses the portal URL. If I modify it to the correct container name, it will work. It is defined in file [2], but it's packaged in eXoGadgets. So, how can we override it? I tried by making a copy of eXoGadgets to the extension and registering it in clienta-config.jar/conf/configuration.xml, no success... For ServicesManagement the questions is: how can we override the gadget preferences? [1] eXoGadgets/src/main/webapp/gadgets/ServicesManagement/script/script.js ServicesManagement.prototype.init = function() { var monitor = eXo.gadget.ServicesManagement; var prefs = new _IG_Prefs(); var servicesURL = prefs.getString("servicesURL"); if (servicesURL && $.trim(servicesURL) != "") { monitor.SERVICES_URL = $.trim(servicesURL); } else { monitor.SERVICES_URL = monitor.DEFAULT_SERVICES_URL; } ... monitor.makeRequest(monitor.SERVICES_URL, monitor.renderServiceSelector); }; [2] eXoGadgets.war/gadgets/ServicesManagement/ServicesManagement.xml <UserPref name="servicesURL" display_name="__MSG_services_url__" default_value="/portal/rest/management" required="true"/> <Content type="html" view="home">
Cannot reproduce with the upcoming JPP 6.1.1 DR1
The issue is reproducible on JPP 6.1.0 GA.
Reproducible on 6.1.0.GA, cannot reproduce on 6.1.1.DR1 and DR2 - changing to verified.