[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-886) Instantiate jbpmConfiguration eager despite no process-definition list
by Ciro Cavani (JIRA)
Instantiate jbpmConfiguration eager despite no process-definition list
----------------------------------------------------------------------
Key: JBSEAM-886
URL: http://jira.jboss.com/jira/browse/JBSEAM-886
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM
Affects Versions: 1.1.6.GA
Reporter: Ciro Cavani
Priority: Optional
Fix For: 1.1.7.GA
I am using ProcessDefinition deployed directly to a "long life" jBPM database (no "create-drop"). No xml with ear package. Because that, jbpmConfiguration on jbpm component is lazy instantiate.
Actual (org.jboss.seam.core.Jbpm):
@Create
public void startup() throws Exception
{
log.trace( "Starting jBPM" );
installProcessDefinitions();
installPageflowDefinitions();
JbpmExpressionEvaluator.setVariableResolver( new SeamVariableResolver() );
}
...
public JbpmConfiguration getJbpmConfiguration()
{
if (jbpmConfiguration==null)
{
initJbpmConfiguration();
}
...
private void installProcessDefinitions()
{
if ( processDefinitions!=null && processDefinitions.length>0 )
{
JbpmContext jbpmContext = getJbpmConfiguration().createJbpmContext();
...
Suggestion:
@Create
public void startup() throws Exception
{
log.trace( "Starting jBPM" );
initJbpmConfiguration(); /*** eager despite xml */
installProcessDefinitions();
installPageflowDefinitions();
JbpmExpressionEvaluator.setVariableResolver( new SeamVariableResolver() );
}
Thanks
--
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
19 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-755) s:selectItems noSelectionLabel broken
by Peter Muir (JIRA)
s:selectItems noSelectionLabel broken
-------------------------------------
Key: JBSEAM-755
URL: http://jira.jboss.com/jira/browse/JBSEAM-755
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.1.5.GA
Reporter: Peter Muir
Priority: Minor
Fix For: 1.1.6.GA
This is broken as in fact using a null value in a SelectItem causes an <option>Label</option> to be rendered, which when submitted actually has a value="Label" (I *think* this is an http think).
To fix this requires adding the ability to chain converters to JSF - create a ChainConverter implements Converter, add the original (user defined) converter at the end of the chain, and then put a new, null, converter at the front of the chain. This might be useful in other circumstances as well.
--
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
19 years, 1 month