[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3147) FacesMessage I18N keys are evaluated differently between "redirect" and "render" navigations
by Michael Youngstrom (JIRA)
FacesMessage I18N keys are evaluated differently between "redirect" and "render" navigations
--------------------------------------------------------------------------------------------
Key: JBSEAM-3147
URL: http://jira.jboss.com/jira/browse/JBSEAM-3147
Project: Seam
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.0.2.SP1
Reporter: Michael Youngstrom
Assigned To: Michael Youngstrom
Fix For: 2.0.3.GA
When using FacesMessages.addFromResourceBundle() message resolution is deferred until after the phase it was added in. Though I'm not exactly sure why it is done this way it is causing problems with "render" vs "redirect" navigations. In the case of a "render" the Pages component changes the current viewID prior to the end of the phase. So when the FacesMessages component processes it's FacesMessages at the end of the phase the viewId is going to be different than what it would be for a "redirect". This can be a problem if you are using Seam Page bundles. IMO the message really should come from the page where the action was invoked not the destination page.
If the FacesMessage component defers FacesMessage creation because it wants to do interpolation after the phase is complete perhaps we can change FacesMessages to immediately look up the message key and then lazily interpolate that message? I can go ahead and fix this if nobody has an objection.
Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3244) TaskInstacePriorityList for pooled actors
by Vinicius Carvalho (JIRA)
TaskInstacePriorityList for pooled actors
------------------------------------------
Key: JBSEAM-3244
URL: https://jira.jboss.org/jira/browse/JBSEAM-3244
Project: Seam
Issue Type: Feature Request
Components: BPM
Reporter: Vinicius Carvalho
Priority: Trivial
Seam provides a TaskInstacePriorityList, which is cool, but sometimes we need to display tasklists for pooled actors not for assigned actors. I've created a component that wraps this, it might be a good idea to put this on next releases.
Regards
package com.furiousbob.components;
import java.io.Serializable;
import java.util.ArrayList;
import java.util.Collections;
import java.util.Comparator;
import java.util.List;
import org.jboss.seam.annotations.AutoCreate;
import org.jboss.seam.annotations.In;
import org.jboss.seam.annotations.Install;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Transactional;
import org.jboss.seam.annotations.Unwrap;
import org.jboss.seam.bpm.Actor;
import org.jbpm.JbpmContext;
import org.jbpm.taskmgmt.exe.TaskInstance;
@Name("pooledTaskPriorityList")
@AutoCreate
@Install(dependencies="org.jboss.seam.bpm.jbpm")
public class PooledTaskPriority implements Serializable {
@In
private Actor actor;
@In
private JbpmContext jbpmContext;
@SuppressWarnings("unchecked")
@Unwrap
@Transactional
public List<TaskInstance> getTaskPriority(){
List<TaskInstance> tasks = jbpmContext.getTaskMgmtSession().findPooledTaskInstances(new ArrayList<String>(actor.getGroupActorIds()));
Collections.sort(tasks, new Comparator<TaskInstance>(){
public int compare(TaskInstance o1, TaskInstance o2) {
return (o1.getPriority() > o2.getPriority()) ? 1 : (o1.getPriority() < o2.getPriority() ? -1 : 0);
}
});
return tasks;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months