[
http://jira.jboss.com/jira/browse/JBSEAM-886?page=comments#action_12353588 ]
Ciro Cavani commented on JBSEAM-886:
------------------------------------
Sorry. I will try clarify my point:
When there is a xml of process definition deployed inside application, jbpm component
instantiate eager jbpmConfiguration in method installProcessDefinitions through
getJbpmConfiguration.
In DVD Store, the database of jBPM is set to "create-drop" and there is some xml
and jbpmConfiguration (with all Persistence startup) is instantiate with the application.
On my setup, I create jBPM database for "long life" use and deploy
ProcessDefinition directly on this database. No xml becouse process definition could
change with application on line (no restart).
That way, jbpm component don't instantiate jbpmConfiguration on startup. Only when I
call Jbpm.instance().getJbpmConfiguration().
I am requesting the same behavior for both case (xml and database deployed
ProcessDefinition). This is not a bug.
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
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