March 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3273) It restores all pre-defined configuration when re-creating a site config with the same name

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3273?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3273: ---------------------------------- Fix Version/s: 3.7.1.Final (was: 3.7.0.Final) > It restores all pre-defined configuration when re-creating a site config with the same name > ------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3273 > URL: https://issues.jboss.org/browse/GTNPORTAL-3273 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.6.Final, 3.6.1.Final > Reporter: Trong Tran > Fix For: 3.7.1.Final > > > Steps to reproduce: > - Login with root > - Edit the home page layout to add the Organization Porltet > - In Organization portlet, go to delete the pre-defined group /organization/management/executive-board. You will notice that it also deletes all data (navigation nodes, pages) belonging to that group > - Then re-create a group with the same name under /organization/management/. > ===> Now you will see that all pre-defined data is restored as the first initializing time. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3365: ---------------------------------- Fix Version/s: 3.7.1.Final (was: 3.7.0.Final) > Exception swallow in UserDaoImpl.persistUserInfo() > -------------------------------------------------- > > Key: GTNPORTAL-3365 > URL: https://issues.jboss.org/browse/GTNPORTAL-3365 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.6.3.Final > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > Fix For: 3.6.4.Final, 3.7.1.Final > > Original Estimate: 4 hours > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > Under "{{org.exoplatform.services.organization.idm}}, > focus on : > {code:title=UserDAOImp.java|borderStyle=solid} > public void persistUserInfo(User user, IdentitySession session) throws Exception > { > orgService.flush(); > AttributesManager am = session.getAttributesManager(); > ArrayList attributes = new ArrayList(); > /* ... */ > if (user.getPassword() != null) > { > if (orgService.getConfiguration().isPasswordAsAttribute()) > { > attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword())); > } > else > { > try > { > am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword()); > } > catch (IdentityException e) > { > log.info("Cannot update password: " + user.getUserName() + "; ", e); > } > } > } > Attribute[] attrs = new Attribute[attributes.size()]; > attrs = (Attribute[])attributes.toArray(attrs); > try > { > am.updateAttributes(user.getUserName(), attrs); > } > catch (IdentityException e) > { > log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e); > } > } > {code} > > The method {{saveUser(User, boolean) _throws Exception_}} > calls > {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}. > > Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}: > * first time in the password level > * second time when updating all of the attributes. > (!) Users want to be notified when an error occurs during user registration. > As well as being aware of the type of the caught exception. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3426: ---------------------------------- Fix Version/s: 3.7.0.Final > CDI portlet throws an exception during deployment > -------------------------------------------------- > > Key: GTNPORTAL-3426 > URL: https://issues.jboss.org/browse/GTNPORTAL-3426 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final, 3.8.0.Final > > > From Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1075588 > CDI portlet > Any CDI portlet will currently this exception during deployment > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > You can find full stack trace here - http://pastebin.com/b8WYRrhy > I am also enclosing one CDI portlet for easy reproduction. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3366) [IE8, IE9] Can not rename Dashboard tab if name contains accent chars

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3366?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3366: ---------------------------------- Fix Version/s: 3.7.1.Final (was: 3.7.0.Final) > [IE8, IE9] Can not rename Dashboard tab if name contains accent chars > --------------------------------------------------------------------- > > Key: GTNPORTAL-3366 > URL: https://issues.jboss.org/browse/GTNPORTAL-3366 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Tran Trung Thanh > Fix For: 3.5.9.Final, 3.7.1.Final > > > Steps to reproduce: > - Login > - Create a Dashboard page > - Go to that page, create a new tab of which name contains accent chars (i.e. sổ mũi khéo dài) > - Edit name of that tab by deleting some chars in the name (i.e.: sổ mũi) > - Hit Enter > >>> Result: can not rename -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3368: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.0.Final Resolution: Done > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final, 3.8.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3414) Be able to intercept and process oauth principal into gatein user according to provider types

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.pl... ] Trong Tran resolved GTNPORTAL-3414. ----------------------------------- Fix Version/s: 3.7.0.Final 3.8.0.Final Resolution: Done > Be able to intercept and process oauth principal into gatein user according to provider types > --------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Fix For: 3.7.0.Final, 3.8.0.Final > > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Time Spent: 7 hours > Remaining Estimate: 0 minutes > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNCOMMON-17) NPE when decode a value encoded from latin character

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNCOMMON-17?page=com.atlassian.jira.plug... ] Peter Palaga resolved GTNCOMMON-17. ----------------------------------- Fix Version/s: 2.2.2.Final Resolution: Done > NPE when decode a value encoded from latin character > ---------------------------------------------------- > > Key: GTNCOMMON-17 > URL: https://issues.jboss.org/browse/GTNCOMMON-17 > Project: GateIn Common > Issue Type: Bug > Reporter: Khoi Nguyen > Fix For: 2.2.2.Final > > Attachments: encoder.patch > > > I used FastURLEncoder to encode some value like '%FF%EE', however I got a NullPointerException as following > {code} > java.lang.NullPointerException > at org.gatein.common.text.FastURLDecoder$LookupNonTerm.access$100(FastURLDecoder.java:267) > at org.gatein.common.text.FastURLDecoder.safeEncode(FastURLDecoder.java:215) > at org.gatein.common.text.AbstractCharEncoder.encode(AbstractCharEncoder.java:87) > at org.gatein.common.http.TestDecode.main(TestDecode.java:46) > {code} > I also attach a patch for testcase. Look at on it please -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNCOMMON-23) Add support for reversing character entities into chars

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNCOMMON-23?page=com.atlassian.jira.plug... ] Peter Palaga resolved GTNCOMMON-23. ----------------------------------- Fix Version/s: 2.2.2.Final Resolution: Done > Add support for reversing character entities into chars > ------------------------------------------------------- > > Key: GTNCOMMON-23 > URL: https://issues.jboss.org/browse/GTNCOMMON-23 > Project: GateIn Common > Issue Type: Feature Request > Reporter: Juraci Paixão Kröhling > Fix For: 2.2.2.Final > > > The EntityEncoder currently has means to convert a given input into character entities, meant to be safe for display as HTML. As part of GTNPORTAL-3400, we need a way to do the reverse: get the char for a given character entity. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3414) Be able to intercept and process oauth principal into gatein user according to provider types

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3414: ---------------------------------- Summary: Be able to intercept and process oauth principal into gatein user according to provider types (was: Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension) > Be able to intercept and process oauth principal into gatein user according to provider types > --------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Time Spent: 7 hours > Remaining Estimate: 0 minutes > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3430) Missing icons on Permissions tab

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3430?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3430: ---------------------------------------------------- Lucas Ponce <lponce(a)redhat.com> changed the Status of [bug 1078704|https://bugzilla.redhat.com/show_bug.cgi?id=1078704] from ASSIGNED to POST > Missing icons on Permissions tab > -------------------------------- > > Key: GTNPORTAL-3430 > URL: https://issues.jboss.org/browse/GTNPORTAL-3430 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > "Permissions tab" on "Site's Config" only has icon on "Edit" sub-tab. > It looks like there are 3 missing icons for: "Access", "Move Apps" and "Move Containers" -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2014