November 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-807?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-807: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > Allow assignment of jBPM variables via EL evaluation > ---------------------------------------------------- > > Key: JBPM-807 > URL: https://jira.jboss.org/jira/browse/JBPM-807 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Priority: Critical > Fix For: jBPM 3.3.2 GA > > > A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. > What I want is to be able to say: > <assign variable="orderId" value="#{order.id}"/> > when a transition occurs. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1016) ProcessState 'leave' method always returns default transition

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1016?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1016: --------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > ProcessState 'leave' method always returns default transition > -------------------------------------------------------------- > > Key: JBPM-1016 > URL: https://jira.jboss.org/jira/browse/JBPM-1016 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.2.0 > Reporter: Randy Gullett > Fix For: jBPM 3.3.2 GA > > > The leave method for ProcessStates currently automatically takes the default transition despite taking a transition as a parameter. Can it be modified so that it leaves by the transition passed in (if it isn't null) like you'd expect it to? I want to be able to short-circuit my subprocesses in certain scenarios. See the method as it's currently coded below. > public void leave(ExecutionContext executionContext, Transition transition) { > ProcessInstance subProcessInstance = executionContext.getSubProcessInstance(); > Token superProcessToken = subProcessInstance.getSuperProcessToken(); > // feed the readable variableInstances > if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { > ContextInstance superContextInstance = executionContext.getContextInstance(); > ContextInstance subContextInstance = subProcessInstance.getContextInstance(); > // loop over all the variable accesses > Iterator iter = variableAccesses.iterator(); > while (iter.hasNext()) { > VariableAccess variableAccess = (VariableAccess) iter.next(); > // if this variable access is writable > if (variableAccess.isWritable()) { > // the variable is copied from the sub process mapped name > // to the super process variable name > String mappedName = variableAccess.getMappedName(); > Object value = subContextInstance.getVariable(mappedName); > String variableName = variableAccess.getVariableName(); > log.debug("copying sub process var '"+mappedName+"' to super process var '"+variableName+"': "+value); > if (value!=null) { > superContextInstance.setVariable(variableName, value, superProcessToken); > } > } > } > } > // fire the subprocess ended event > fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext); > // remove the subprocess reference > superProcessToken.setSubProcessInstance(null); > > // We replaced the normal log generation of super.leave() by creating the log here > // and overriding the addNodeLog method with an empty version > superProcessToken.addLog(new ProcessStateLog(this, superProcessToken.getNodeEnter(), new Date(), subProcessInstance)); > // call the subProcessEndAction > [b]super.leave(executionContext, getDefaultLeavingTransition());[/b] } > The bold line could be replaced by something like: > if(transition != null) { > super.leave(executionContext, transition); > } else { > super.leave(executionContext, getDefaultLeavingTransition()); -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1023) 3.2.1 Admin Console: No download for AS 4.2 with Java 5

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1023?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1023: --------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > 3.2.1 Admin Console: No download for AS 4.2 with Java 5 > ------------------------------------------------------- > > Key: JBPM-1023 > URL: https://jira.jboss.org/jira/browse/JBPM-1023 > Project: JBoss jBPM > Issue Type: Bug > Components: Console > Reporter: Burr Sutter > Fix For: jBPM 3.3.2 GA > > > The current 3.2.1 jPDL Suite download doesn't produce a WAR that runs on AS 4.2 with Java 5. The offending jar seems to be gravel-14.jar -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-963) NullPointerException in the Eclipse plugin

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-963?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-963: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > NullPointerException in the Eclipse plugin > ------------------------------------------ > > Key: JBPM-963 > URL: https://jira.jboss.org/jira/browse/JBPM-963 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.2.0 > Environment: WinXP SP2 Eclipse 3.2.1, JDK 1.5.0_11 and/or JDK 1.4.2_13 > Reporter: Oleksandr Alesinskyy > Fix For: jBPM 3.3.2 GA > > > Hello, > I have downloaded and installed jBPM suite 3.2GA then I have installed Eclipse plugin from that suite into pre-existing Eclipse 3.2.1 (by copying contents of designer/eclipse directory to Eclipse extesions directory) and have created new JBoss JBPM Process project (with sample contents) - all succesfully. Then I have checked in the project into CVS. After this on Eclise restart comes message "Can not initialize JDT tooling" and following error stack: > java.lang.NullPointerException > at org.jbpm.ui.util.JbpmClasspathContainer.getJarNames(Unknown Source) > at org.jbpm.ui.util.JbpmClasspathContainer.createJbpmLibraryEntries(Unknown Source) > at org.jbpm.ui.util.JbpmClasspathContainer.getClasspathEntries(Unknown Source) > at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:494) > at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4119) > at org.jbpm.ui.util.JbpmClasspathContainerInitializer.initialize(Unknown Source) > at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900) > at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267) > at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470) > at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169) > at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073) > at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4189) > at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize(JREContainerInitializer.java:57) > at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900) > at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267) > at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470) > at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169) > at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073) > at org.eclipse.jdt.internal.core.JavaModelManager.determineIfOnClasspath(JavaModelManager.java:808) > at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:697) > at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:626) > at org.eclipse.jdt.core.JavaCore.create(JavaCore.java:1383) > at org.eclipse.jdt.internal.ui.ResourceAdapterFactory.getAdapter(ResourceAdapterFactory.java:44) > at org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:63) > at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:256) > at org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:66) > at org.eclipse.jdt.internal.ui.filters.NamePatternFilter.select(NamePatternFilter.java:62) > at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.isFiltered(ProblemTreeViewer.java:187) > at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.isFiltered(PackageExplorerPart.java:301) > at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.isExpandable(ProblemTreeViewer.java:174) > at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:1900) > at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2487) > at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:754) > at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:731) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:705) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:892) > at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1288) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1323) > at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.preservingSelection(PackageExplorerPart.java:404) > at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1277) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:250) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1542) > at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.createPartControl(PackageExplorerPart.java:638) > at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:332) > at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197) > at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566) > at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:3915) > at org.eclipse.ui.internal.WorkbenchPage.restoreState(WorkbenchPage.java:2929) > at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1936) > at org.eclipse.ui.internal.Workbench.doRestoreState(Workbench.java:2857) > at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:2805) > at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1681) > at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:1421) > at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1679) > at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1650) > at org.eclipse.ui.internal.Workbench$17.run(Workbench.java:1529) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1473) > at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183) > at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:702) > at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) > at org.eclipse.core.launcher.Main.basicRun(Main.java:280) > at org.eclipse.core.launcher.Main.run(Main.java:977) > at org.eclipse.core.launcher.Main.main(Main.java:952) > and Eclipse package explorer becomes unavailable. > The same occurs if I install plugin on other computer and check-out the project and restart Eclipse. I#m still able to create another new jBPM Process project and work with it. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-993) make assignment handlers configurable

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-993?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-993: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > make assignment handlers configurable > ------------------------------------- > > Key: JBPM-993 > URL: https://jira.jboss.org/jira/browse/JBPM-993 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.4 > Environment: N/A > Reporter: Martin Goldhahn > Priority: Minor > Fix For: jBPM 3.3.2 GA > > Attachments: assignment-handler.patch > > > The JpdlXmlReader contains a hard-coded reference to both org.jbpm.identity.assignment.ExpressionAssignmentHandler and org.jbpm.taskmgmt.assignment.ActorAssignmentHandler. > We need this parameter to be configurable, e.g. being able to use our own ExpressionAssignmentHandler -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-569) improve EL expression examples in the user guide

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-569?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-569: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: https://jira.jboss.org/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Fix For: jBPM 3.3.2 GA > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-955) jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-955?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-955: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes) > ---------------------------------------------------------------------------------- > > Key: JBPM-955 > URL: https://jira.jboss.org/jira/browse/JBPM-955 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.2.0 > Environment: All > Reporter: Arjan van Bentem > Priority: Minor > Fix For: jBPM 3.3.2 GA > > > Currently, an Actor or Swimlane is assigned within the task definition. When using sub-processes it would be very convenient to make the assignments in the parent process, such as in the parent <process-state>, or maybe even in the outermost <process-definition>. > For example: both a helpdesk employee and the customer would need to fill in the same questionnaire at different points in the main process. The steps to fill in the questionnaire would be a generic sub-process, in which (at design time) one would not know the Swimlane nor Actor. This would require a way to set the swimlane in the parent's process-state: >  > <process-state name="Customer survey" swimlane="client"> > <sub-process name="survey" /> > </process-state> > : > : > <process-state name="Employee survey" swimlane="employer"> > <sub-process name="survey" /> > </process-state> > ... or > <process-state name="Employee survey"> > <assignment actor-id="..."/> > <sub-process name="survey" /> > </process-state> > ... or maybe even at an even higher level, where jBPM would iterate up into the chain, possibly though nested sub-processes, until some assignment is found? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-996) Add ESB Service Node to jpdl and jpdl-designer

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-996?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-996: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > Add ESB Service Node to jpdl and jpdl-designer > ---------------------------------------------- > > Key: JBPM-996 > URL: https://jira.jboss.org/jira/browse/JBPM-996 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: The ESB has an ESBActionHandler that can be manually configured at each node representing an ESB service in a jPDL processdefinition. A new node type of service-node, that is supported through the jpdl designer, would make it easier for the user to add these sevices, as the designer would know what properties are required for the user to provide. > A nice thing about the ESB from a jBPM perspective (and an ESB Service Node) is that it gives jBPM access to practically any type of service through the same node-type, e.g., web services, rule services, jms queues, file transfer services, etc. So if jBPM has a service node, it eliminates the need to create lots of other specialized node types in jBPM, and less of a need for customers to create custom action handlers. > Reporter: Jeff DeLong > Fix For: jBPM 3.3.2 GA > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1078) Bug when designing process if node has "/" in his name

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1078?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1078: --------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > Bug when designing process if node has "/" in his name > ------------------------------------------------------ > > Key: JBPM-1078 > URL: https://jira.jboss.org/jira/browse/JBPM-1078 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.2.2 > Environment: eclipse 3.3, ubuntu linux 6.10, jdk 1.5 > Reporter: Andraz Skoric > Priority: Minor > Fix For: jBPM 3.3.2 GA > > > If you have 2 nodes and the second one includes char / in his name you cannot make a transition from node 1 to node 2. Transition is pointed into upper left corner and not to node 2. If you manually code transition it looks fine, but one you restart your workspace the problem comes back. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-567) create reusable JSF UI components in webapp

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-567?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-567: -------------------------------- Fix Version/s: jBPM 3.3.2 GA Revisit issues that have votes > create reusable JSF UI components in webapp > ------------------------------------------- > > Key: JBPM-567 > URL: https://jira.jboss.org/jira/browse/JBPM-567 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Reporter: Tom Baeyens > Fix For: jBPM 3.3.2 GA > > > We plan to package the building blocks of the webapplication as reusable JSF UI components. Candidates are : the task list, the list of process definitions you can start, the task form, ... One of the main objectives of creating these components is that this will be the reuse done between the plain webapplication and using jBPM in a portal. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2008