[JBoss JIRA] (GTNPORTAL-3245) Add comfriming when user remove permissions on edit page & site
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3245?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3245:
----------------------------------
Remaining Estimate: 1 hour (was: 0 minutes)
> Add comfriming when user remove permissions on edit page & site
> ---------------------------------------------------------------
>
> Key: GTNPORTAL-3245
> URL: https://issues.jboss.org/browse/GTNPORTAL-3245
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Hai Nguyen
> Assignee: Hai Nguyen
> Priority: Minor
> Labels: backlogs
> Original Estimate: 4 hours
> Time Spent: 2 days, 3 hours
> Remaining Estimate: 1 hour
>
> - Login portal
> - Go to user and group management
> - Choose Group management tab
> - Add new group ( ex: AAA)
> - Go to Pages
> - Add new page for group above
> - Search this page and click edit
> - Click view page properties
> - Change access and edit permission to ( organization/*)
> - Click Finish button on Editor composer
> => Unknown error and throw exception in console
> {noformat}
> 2013-08-08 15:20:18,549 | ERROR | Error during the processAction phase [portal:UIPortalApplication<http-nio-0.0.0.0-8080-exec-10>]
> java.lang.NullPointerException: null
> at org.exoplatform.portal.webui.portal.UIPortalComposer$FinishPageEditionActionListener.execute(UIPortalComposer.java:680) ~[exo.portal.webui.portal-3.5.6-PLF.jar:3.5.6-PLF]
>
> {noformat}
>
> Reproduce on edit site is the same
--
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
12 years, 5 months
[JBoss JIRA] (GTNPORTAL-3283) Eliminate the Warning "JBAS018204: Clustering not supported, falling back to non-clustered session manager"
by Marko Strukelj (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3283?page=com.atlassian.jira.pl... ]
Marko Strukelj commented on GTNPORTAL-3283:
-------------------------------------------
This happens as a result of deploying a .war marked <distributable /> into a container that's not currently in clustered configuration, but a standalone one.
You need archives marked <distributable /> when running in clustered mode otherwise session replication will not work across cluster.
<distributable /> marks a web application as _being capable_ of properly running in clustered mode, not _requesting to be run_ in clustered mode. It should not IMHO result in a WARN by jboss-web container.
Removing <distributable /> is IMHO not an option, as it would require special manual steps to modify packaged GateIn wars - e.g. portal.war/WEB-INF/web.xml for deploying in cluster mode, and most of the people would probably forget that step, and have to deal with troubleshooting why session replication doesn't work.
Either there is something in web subsystem configuration to turn these WARN logs off, or we can add a logging filter that would mute org.jboss.web WARN level which would be a big hack, and is not really a serious proposition.
> Eliminate the Warning "JBAS018204: Clustering not supported, falling back to non-clustered session manager"
> -----------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3283
> URL: https://issues.jboss.org/browse/GTNPORTAL-3283
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Packaging
> Reporter: Peter Palaga
> Assignee: Marko Strukelj
> Fix For: 3.7.0.Final
>
>
> There are two occurences of this warning in GateIn startup log on JBoss
> {code}
> 09:24:30,563 WARN [org.jboss.web] (MSC service thread 1-2) JBAS018204: Clustering not supported, falling back to non-clustered session manager
> 09:24:30,566 WARN [org.jboss.web] (MSC service thread 1-3) JBAS018204: Clustering not supported, falling back to non-clustered session manager
> 0
> {code}
> These warnings should be eliminated, if possible, as there should be no warnings during startup of an out of the box GateIn instance.
--
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
12 years, 5 months
[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:
---------------------------------
Sprint: Sprint 82
> 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
12 years, 5 months
[JBoss JIRA] (GTNPORTAL-3283) Eliminate the Warning "JBAS018204: Clustering not supported, falling back to non-clustered session manager"
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3283:
---------------------------------------
Summary: Eliminate the Warning "JBAS018204: Clustering not supported, falling back to non-clustered session manager"
Key: GTNPORTAL-3283
URL: https://issues.jboss.org/browse/GTNPORTAL-3283
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Packaging
Reporter: Peter Palaga
Assignee: Marko Strukelj
Fix For: 3.7.0.Final
There are two occurences of this warning in GateIn startup log on JBoss
{code}
09:24:30,563 WARN [org.jboss.web] (MSC service thread 1-2) JBAS018204: Clustering not supported, falling back to non-clustered session manager
09:24:30,566 WARN [org.jboss.web] (MSC service thread 1-3) JBAS018204: Clustering not supported, falling back to non-clustered session manager
0
{code}
These warnings should be eliminated, if possible, as there should be no warnings during startup of an out of the box GateIn instance.
--
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
12 years, 5 months
[JBoss JIRA] (GTNPORTAL-3282) Eliminate the "using a private module org.apache.cxf:main" warning on JBoss startup
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3282:
---------------------------------------
Summary: Eliminate the "using a private module org.apache.cxf:main" warning on JBoss startup
Key: GTNPORTAL-3282
URL: https://issues.jboss.org/browse/GTNPORTAL-3282
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WSRP integration
Reporter: Peter Palaga
Assignee: Chris Laprun
Fix For: 3.7.0.Final
There are several warnings like this in GateIn startup log on JBoss:
{code}
09:24:27,528 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.extension-war.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
09:24:27,551 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-admin-gui.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
09:24:27,556 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-producer.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
09:24:27,557 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-producer.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
09:24:28,561 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
{code}
Searching for "org.apache.cxf" in GateIn source tree shows occurences in {{org.gatein.wsrp.integration}} {{module.xml}}: https://github.com/gatein/gatein-portal/blob/master/packaging/jboss-as7/m...
These warning should be eliminated if possible as there should be no warnings in an out of the box GateIn installation.
--
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
12 years, 5 months
[JBoss JIRA] (GTNPORTAL-3281) On GateIn shutdown: WARN [exo.jcr.component.core.RepositoryImpl] Repository repository is OFFLINE
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3281:
---------------------------------------
Summary: On GateIn shutdown: WARN [exo.jcr.component.core.RepositoryImpl] Repository repository is OFFLINE
Key: GTNPORTAL-3281
URL: https://issues.jboss.org/browse/GTNPORTAL-3281
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: WSRP integration
Reporter: Peter Palaga
Assignee: Chris Laprun
Fix For: 3.7.0.Final
The above Warning is logged during GateIn shutdown. There should be no warnings in an out of the box instance of GateIn.
The stack during the warning is as follows:
{code}
Thread [Thread-68] (Suspended (breakpoint at line 155 in LocationAwareSLF4JExoLog))
LocationAwareSLF4JExoLog.warn(Object) line: 155
RepositoryImpl.getSystemSession(String) line: 400
RepositoryImpl.getSystemSession(String) line: 81
SessionProvider.getSession(String, ManageableRepository) line: 202
JCRPersister$WSRPSessionLifeCycle(JCRPersister$AbstractSessionLifeCycle).login() line: 82
ChromatticImpl.openSession() line: 58
JCRPersister(BaseChromatticPersister).getSession() line: 109
JCRProducerConfigurationService.getPersistedLastModifiedForConfiguration() line: 128
JCRProducerConfigurationService(AbstractProducerConfigurationService).getConfiguration() line: 48
WSRPProducerImpl.getProducerConfiguration() line: 346
WSRPProducerImpl.getProducerRegistrationRequirements() line: 193
WSRPProducerImpl.stop() line: 417
WSRPServiceIntegration.stopProducer() line: 381
WSRPServiceIntegration.stop() line: 375
GeneratedMethodAccessor121.invoke(Object, Object[]) line: not available
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
Method.invoke(Object, Object...) line: 606
LifecycleVisitor.traverse(Container) line: 98
LifecycleVisitor.stop(Container) line: 166
ConcurrentContainer.stop() line: 463
CachingContainer(AbstractContainer).stop() line: 75
ManageableContainer(AbstractContainer).stop() line: 75
ManageableContainer.stop() line: 240
PortalContainer(AbstractContainer).stop() line: 75
PortalContainer(ExoContainer).stop() line: 273
PortalContainer.stop() line: 689
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
Method.invoke(Object, Object...) line: 606
LifecycleVisitor.traverse(Container) line: 98
LifecycleVisitor.stop(Container) line: 166
ConcurrentContainer.stop() line: 463
CachingContainer(AbstractContainer).stop() line: 75
ManageableContainer(AbstractContainer).stop() line: 75
ManageableContainer.stop() line: 240
RootContainer(AbstractContainer).stop() line: 75
RootContainer(ExoContainer).stop() line: 273
RootContainer.stop() line: 1230
RootContainer$ShutdownThread$1.run() line: 1220
RootContainer$ShutdownThread$1.run() line: 1217
SecurityHelper.doPrivilegedAction(PrivilegedAction<E>) line: 290
RootContainer$ShutdownThread.run() line: 1216
{code}
--
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
12 years, 5 months
[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:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.7.0.Final
Resolution: Done
> 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
> Fix For: 3.7.0.Final
>
>
> 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)}}
> The same holds for {{GateInSkinConfigRemoval}}
--
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
12 years, 5 months
[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:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/681
> 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)}}
> The same holds for {{GateInSkinConfigRemoval}}
--
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
12 years, 5 months
[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:
------------------------------------
Description:
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)}}
The same holds for {{GateInSkinConfigRemoval}}
was: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)}}
> 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)}}
> The same holds for {{GateInSkinConfigRemoval}}
--
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
12 years, 5 months