[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-886) Instantiate jbpmConfiguration eager despite no process-definition list

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-886?page=all ]

Gavin King closed JBSEAM-886.
-----------------------------

    Resolution: Won't Fix

> 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