[
http://jira.nuxeo.org/browse/NXP-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Russel closed NXP-2046.
---------------------------------
Resolution: Fixed
page-workflow is not used anymore in nuxeo, so configuration was commented out
from components.xml,
=> only the jbpm variable resolver is used.
(commit 29913)
> SeamVariableResolver is used for jbpm workflow
> ----------------------------------------------
>
> Key: NXP-2046
> URL: http://jira.nuxeo.org/browse/NXP-2046
> Project: Nuxeo Enterprise Platform 5
> Issue Type: Bug
> Components: Workflow
> Reporter: Alexandre Russel
> Assignee: Alexandre Russel
> Priority: Major
>
> To use the workspace creation wizard, pageflow is used, adding:
> <core:jbpm>
> <core:pageflow-definitions>
> %{PAGEFLOW}%
> </core:pageflow-definitions>
> </core:jbpm>
> to components.xml.
> When initialising this component, seam set jbpm variable resolver to the jbpm
> variable resolver:
> @Create
> public void startup() throws Exception
> {
> log.trace( "Starting jBPM" );
> installProcessDefinitions();
> installPageflowDefinitions();
> JbpmExpressionEvaluator.setVariableResolver( new SeamVariableResolver()
> );
> }
> It is understood that using seam resolver for jbpm is not wanted because a
> seam context may not be present.
> When seam resolver doesn't find a variable in its context, it doesn't go get
> one in jbpm context.
> However setting it back to jbpmVariable resolver, or commenting out the conf
> file may create big badaboum in the workspace creaion wizard.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
