[JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.pl... ]
Peter Palaga commented on GTNPORTAL-3368:
-----------------------------------------
Thanks for the report, Trong.
How did you build the quickstart? The thing is that we have changed our development model for quickstarts cca 4 weeks ago. The main relevant points are two:
(1) GateIn compatibility is no strict requirement for quickstarts anymore, but it is nice to have and best effort only.
(2) {{master}} branch is not maintained anymore. There is {{6.1.x-develop}} which is supposed to work with JBoss Portal 6.1.x
I guess you built from {{master}}. If so, could you please try using {{6.1.x-develop}}? https://github.com/jboss-developer/jboss-portal-quickstarts/tree/6.1.x-de...
> 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: Peter Palaga
> Fix For: 3.7.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
12 years, 2 months
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?focusedWorklogId=12430469&... ]
Vu Viet Phuong logged work on GTNPORTAL-3365:
---------------------------------------------
Author: Vu Viet Phuong
Created on: 15/Jan/14 5:51 AM
Start Date: 15/Jan/14 5:50 AM
Worklog Time Spent: 6 hours
Work Description: There is 2 problem on Picketlink, so I have to make workaround on the PR to fix for this case. The 2 issues are:
1. Picketlink has not support transaction for LDAP yet
2. Picketlink uses internal cache (infinispan) but this cache is not clear when there is exception occurred
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 6 hours
Worklog Id: (was: 12430469)
> 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
> 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
12 years, 2 months
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ]
Vu Viet Phuong updated GTNPORTAL-3365:
--------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/765
> 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
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> 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
12 years, 2 months