[JBoss JIRA] (GTNPORTAL-3280) Remove only what was added in JavascriptConfigDeployer and GateInSkinConfigDeployer
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3280?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3280:
------------------------------------
Summary: Remove only what was added in JavascriptConfigDeployer and GateInSkinConfigDeployer (was: Remove only what was added in JavascriptConfigDeployer)
> Remove only what was added in JavascriptConfigDeployer and GateInSkinConfigDeployer
> -----------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3280
> URL: https://issues.jboss.org/browse/GTNPORTAL-3280
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> Calling {{org.exoplatform.portal.resource.MainResourceResolver.removeServletContext(ServletContext)}} (via {{org.exoplatform.portal.resource.AbstractResourceService.unregisterServletContext(WebApp)}}) from {{org.exoplatform.web.application.javascript.JavascriptConfigDeployer.remove(WebApp)}} results in several unnecessary warnings during server shutdown and portal container reload. The cause is that only contexts having {{/WEB-INF/gatein-resources.xml}} are registered, but one tries to unregister all contexts, no matter if they contain {{/WEB-INF/gatein-resources.xml}} or not. The fix should add the "has resources.xml" condition also on removal in {{org.exoplatform.web.application.javascript.JavascriptConfigDeployer.remove(WebApp)}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (GTNPORTAL-3280) Remove only what was added in JavascriptConfigDeployer
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3280:
---------------------------------------
Summary: Remove only what was added in JavascriptConfigDeployer
Key: GTNPORTAL-3280
URL: https://issues.jboss.org/browse/GTNPORTAL-3280
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Peter Palaga
Assignee: Peter Palaga
Calling {{org.exoplatform.portal.resource.MainResourceResolver.removeServletContext(ServletContext)}} (via {{org.exoplatform.portal.resource.AbstractResourceService.unregisterServletContext(WebApp)}}) from {{org.exoplatform.web.application.javascript.JavascriptConfigDeployer.remove(WebApp)}} results in several unnecessary warnings during server shutdown and portal container reload. The cause is that only contexts having {{/WEB-INF/gatein-resources.xml}} are registered, but one tries to unregister all contexts, no matter if they contain {{/WEB-INF/gatein-resources.xml}} or not. The fix should add the "has resources.xml" condition also on removal in {{org.exoplatform.web.application.javascript.JavascriptConfigDeployer.remove(WebApp)}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (GTNPORTAL-511) userPref of gadgets are not sometime not saved correctly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-511?page=com.atlassian.jira.plu... ]
Trong Tran updated GTNPORTAL-511:
---------------------------------
Fix Version/s: 3.5.7.Final
(was: 4.x)
> userPref of gadgets are not sometime not saved correctly
> --------------------------------------------------------
>
> Key: GTNPORTAL-511
> URL: https://issues.jboss.org/browse/GTNPORTAL-511
> Project: GateIn Portal
> Issue Type: Bug
> Components: User Interface
> Affects Versions: 3.0.0-Beta04
> Environment: svn r1330
> Reporter: jerem j
> Assignee: Julien Viet
> Fix For: 3.5.7.Final
>
> Attachments: GTNPORTAL-511.js.patch, GTNPORTAL-511.patch, stacktrace.txt
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Every call to gadgets.Prefs.set generate a call to save the data in the backend (an action in the dashboard portlet). To save we send all the set of preferences.
> The jira gadget call this API multiple times in a very short time. So there is multiple ajax request sent to the backend but not in a precise order. So it might happen that the first request arrive the last one, and so old preferences are saved.
> To fix:
> In the file Gadgets.js, function "gadgets.IfrGadgetService.prototype.setUserPref", prefs is updated with all the name/value, and ALL the prefs object is saved. Instead of saving all the preferences, we should only save the updated preferences.
> In org.exoplatform.portal.pom.spi.gadget.Gadget it will be needed to be able to add preference by name, something like :
> public void setUserPref(String name, String value)
> code :
> Gadgets.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResour...
> ExoBasedUserPrefStore.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResour...
> links:
> API doc about adgets.Prefs.set: http://code.google.com/apis/gadgets/docs/reference/#gadgets.Prefs.set
> Jira gadget to test: http://jira4j.exoplatform.org/rest/gadgets/1.0/g/com.atlassian.jira.gadge...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month