November 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-233) Delete a Timer in a TaskNode

by Sven Daumann (JIRA)

Delete a Timer in a TaskNode ---------------------------- Key: GPD-233 URL: https://jira.jboss.org/jira/browse/GPD-233 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.3 Environment: Eclipse 3.3.2, JPDL Designer 3.1.2, 3.1.3sp2 Reporter: Sven Daumann Assignee: Koen Aers step1: Create a timer in the properties-menu of a TaskNode step2: Delete the created timer in the menu problem: The timer is still visible. The timer is also visible after changing the tabs workaround: deselect the TaskNode Repeating step 1 and 2 with creating an event works fine. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-133) with two transitions from a node, both need to be labelled, or jbpm-console exceptions

by Ross McDonald (JIRA)

with two transitions from a node, both need to be labelled, or jbpm-console exceptions -------------------------------------------------------------------------------------- Key: GPD-133 URL: http://jira.jboss.com/jira/browse/GPD-133 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.beta1 Environment: osx, macbook pro, eclipse 3.3.0 Reporter: Ross McDonald Assigned To: Koen Aers when there are two transitions from a node, both need to be labelled (given a name), I am not sure if there is a validate xml option within the plugin, it would help if there was, if both are not given a name, the jbpm-console exceptions across multiple pages -- 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

16 years, 8 months

2
21
0 / 0

[JBoss JIRA] Created: (GPD-204) Additional Attribute for ESB Service Node

by Jeff DeLong (JIRA)

Additional Attribute for ESB Service Node ----------------------------------------- Key: GPD-204 URL: http://jira.jboss.com/jira/browse/GPD-204 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Jeff DeLong Assigned To: Koen Aers There are two other options of the ESBActionHandler described in the SOA_ESB_JBPM_Integration_Guide.pdf default - optional attribute which can hold a default value if the esb MVEL expression does not find a value set in the EsbMessage. exceptionTransition - optional element. The name of the transition that should be taken if an exception occurs while processing the Service. This requires the current node to have more then one outgoing transition where one of the transition handles "exception processing" -- 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

16 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (GPD-187) Expose properties of base classes in field/bean configuration of GPD

by s b (JIRA)

Expose properties of base classes in field/bean configuration of GPD -------------------------------------------------------------------- Key: GPD-187 URL: http://jira.jboss.com/jira/browse/GPD-187 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM jPDL Designer 3.1.0.SP1 Environment: Windows XP (and others) Reporter: s b Assigned To: Koen Aers In the process designer interface for setting bean/field properties for custom classes such as an AssignmentHandler, it would be desirable if the properties/fields of the base classes (that the custom class inherits from) are also exposed. Then we could use inheritance much more effectively in our custom class designs. -- 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

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (GPD-162) Deploying a process does not pull in necessary Java classes

by Micah Modell (JIRA)

Deploying a process does not pull in necessary Java classes ----------------------------------------------------------- Key: GPD-162 URL: http://jira.jboss.com/jira/browse/GPD-162 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: RHEL 5 GPD 3.1.0.CR1 Reporter: Micah Modell Assigned To: Koen Aers Attachments: websale.par When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly. 1) Modified an existing process (as per GPD 161). 2) Save the process. (.par will be attached) 3) Use the Deployment tab to deploy the updated process. 4) Execute the process and you get the following error: In the web page: Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown. On the console: 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler' java.lang.NullPointerException at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105) at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48) at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163) at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163) at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>) at org.jbpm.graph.node.Decision.execute(Decision.java:87) at org.jbpm.graph.def.Node.enter(Node.java:318) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:393) at org.jbpm.graph.node.StartState.leave(StartState.java:70) at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>) at org.jbpm.graph.exe.Token.signal(Token.java:194) at org.jbpm.graph.exe.Token.signal(Token.java:139) at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163) at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>) at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476) at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390) at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47) at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82) at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77) at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758) at javax.faces.component.UICommand.broadcast(UICommand.java:368) at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) -- 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

16 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (GPD-174) Develop a jPDL cheatsheet

by Koen Aers (JIRA)

Develop a jPDL cheatsheet ------------------------- Key: GPD-174 URL: http://jira.jboss.com/jira/browse/GPD-174 Project: JBoss jBPM GPD Issue Type: Task Reporter: Koen Aers Assigned To: Koen Aers -- 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

16 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (GPD-183) Cut/Copy/Paste of transitions and nodes in the process designer

by Matthew Sandoz (JIRA)

Cut/Copy/Paste of transitions and nodes in the process designer --------------------------------------------------------------- Key: GPD-183 URL: http://jira.jboss.com/jira/browse/GPD-183 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Matthew Sandoz Assigned To: Koen Aers It would be very useful to support cut/copy/paste in the process designer. These operations would have the challenge of creating new element names where there were conflicts and determining which transitions to carry along - only connected transitions - that is those whose source and target nodes are also in the selection. -- 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

16 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-161) Overwriting a node in the source yields an out-of-sync diagram

by Micah Modell (JIRA)

Overwriting a node in the source yields an out-of-sync diagram -------------------------------------------------------------- Key: GPD-161 URL: http://jira.jboss.com/jira/browse/GPD-161 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: RHEL 5 3.1.0cr1 Reporter: Micah Modell Assigned To: Koen Aers I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process. When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before. I'll attach the before and after JPDL as well as the substitution text after I open this bug. -- 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

16 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (GPD-149) Creating tasks by editing XML source will prevent the XML file from being re-opened

by Jeff Wang (JIRA)

Creating tasks by editing XML source will prevent the XML file from being re-opened ----------------------------------------------------------------------------------- Key: GPD-149 URL: http://jira.jboss.com/jira/browse/GPD-149 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: Eclipse 3.3, Designer 3.1.0 CR Reporter: Jeff Wang Assigned To: Koen Aers When you create new tasks by editing the source, it will break the process definition and not allow you to re-open it in Eclipse. Steps to recreate: 1) Create a new process definition 2) Create a task node using the GUI 3) Switch to the source tab 4) Copy the task xml tag 5) Rename the task name to something unique 6) Close the file 7) Re-open using the JBPM editor -- 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

16 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-141) IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception

by Matthias Hanisch (JIRA)

IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception ------------------------------------------------------------------------------------------------ Key: GPD-141 URL: http://jira.jboss.com/jira/browse/GPD-141 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: Eclipse 3.2 on Windows 2000 Reporter: Matthias Hanisch Assigned To: Koen Aers Following part of my processdefinition.xml: <event type="node-leave"> <action class="x.y.z.MyClass" name="An Action"> <arg> anArg </arg> </action> </event> MyClass is in a jar which is added to the classpath of the Process Project. Saving throws an event loop exception in Error Log View with the following stack. Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null argument; at org.eclipse.jface.util.Assert.isNotNull(Assert.java:150) at org.eclipse.jface.util.Assert.isNotNull(Assert.java:126) at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:577) at org.eclipse.jface.viewers.CheckboxTreeViewer.setCheckedElements(CheckboxTreeViewer.java:431) at org.jbpm.gd.jpdl.deployment.IncludeInDeploymentTreeViewer.setCheckedElements(IncludeInDeploymentTreeViewer.java:61) at org.jbpm.gd.jpdl.deployment.DeploymentForm$17.run(DeploymentForm.java:635) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) The problem is, that DeploymentForm.getElementsToCheckFor() does not respect that MyClass returns null for getCompilationUnit(). As a consequence, setCheckedElements is called with null in the Object[]. -- 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

16 years, 8 months

2
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2009