September 2016 - jboss-jira - Jboss List Archives

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-183?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-183. --------------------------- Resolution: Out of Date > Cut/Copy/Paste of transitions and nodes in the process designer > --------------------------------------------------------------- > > Key: GPD-183 > URL: https://issues.jboss.org/browse/GPD-183 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Matthew Sandoz > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7048) Servlet 3.x metadata-complete="true" does not honour absolute-ordering element

by Darryl Miles (JIRA)

Darryl Miles created WFLY-7048: ---------------------------------- Summary: Servlet 3.x metadata-complete="true" does not honour absolute-ordering element Key: WFLY-7048 URL: https://issues.jboss.org/browse/WFLY-7048 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Darryl Miles Assignee: Stuart Douglas Servlet 3.x metadata-complete="true" does not honour absolute-ordering element. If I have a web.xml that sets metadata-complete="true" in the <web-app> element. The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presense of an <others/> element inside it. So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present. This might also be considered a fast-path to prevent any package scanning for annotations / interfaces. The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs). Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it. I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance). Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-141?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-141. --------------------------- Resolution: Out of Date > IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception > ------------------------------------------------------------------------------------------------ > > Key: GPD-141 > URL: https://issues.jboss.org/browse/GPD-141 > Project: 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 > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > Attachments: gpd-141.diff > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-149?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-149. --------------------------- Resolution: Out of Date > Creating tasks by editing XML source will prevent the XML file from being re-opened > ----------------------------------------------------------------------------------- > > Key: GPD-149 > URL: https://issues.jboss.org/browse/GPD-149 > Project: 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: jeffcwang > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-179) pages.xml doesn't work with pageflow editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-179?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-179. --------------------------- Resolution: Out of Date > pages.xml doesn't work with pageflow editor > ------------------------------------------- > > Key: GPD-179 > URL: https://issues.jboss.org/browse/GPD-179 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > > a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu. > and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get > java.lang.NullPointerException > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186) > at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) > at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) > at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) > at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) > at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-136) Widget is disposed in Task Controller Variables Table

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-136?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-136. --------------------------- Resolution: Out of Date > Widget is disposed in Task Controller Variables Table > ----------------------------------------------------- > > Key: GPD-136 > URL: https://issues.jboss.org/browse/GPD-136 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: Eclipse 3.2.2 on Windows 2000 > Reporter: Matthias Hanisch > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > > Select a Task Node. Go to Properties View. > Select Tasks:<task>:Controller (default). > Add two variables, remove the second. > Error Log view contains the following SWT Exception: > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:3374) > at org.eclipse.swt.SWT.error(SWT.java:3297) > at org.eclipse.swt.SWT.error(SWT.java:3268) > at org.eclipse.swt.widgets.Widget.error(Widget.java:435) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330) > at org.eclipse.swt.widgets.Control.setVisible(Control.java:2642) > at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.applyName(VariableTableItemWrapper.java:164) > at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.cancelEditing(VariableTableItemWrapper.java:150) > at org.jbpm.gd.jpdl.util.VariableTableCellClickedResolver.mouseDown(VariableTableCellClickedResolver.java:25) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > After that, table input is not working anymore ("Mapped Name" column not editable anymore, for example). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-364) Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-364?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-364. --------------------------- Resolution: Out of Date > Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: GPD-364 > URL: https://issues.jboss.org/browse/GPD-364 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 4.0.0.GA > Reporter: Alexandre Navarro > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-33) remember the previous form generation data fields

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-33?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-33. -------------------------- Resolution: Out of Date > remember the previous form generation data fields > ------------------------------------------------- > > Key: GPD-33 > URL: https://issues.jboss.org/browse/GPD-33 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > In the form generation, we currently start from the data entered in the task controller (if any) > Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again. > The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields). > I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-40) A slash character in Node name causes crash. Graphical Process Designer allows the slash to be entered anyway.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-40?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-40. -------------------------- Resolution: Out of Date > A slash character in Node name causes crash. Graphical Process Designer allows the slash to be entered anyway. > -------------------------------------------------------------------------------------------------------------- > > Key: GPD-40 > URL: https://issues.jboss.org/browse/GPD-40 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > The Graphical Process Designer allows the user to enter a Task Node name that includes a slash, such as "Accounting/Finance". The slash causes a crash later on when the process is run, and it isn't obvious what the source of the problem is. Suggestion: somehow prevent the user from entering a name that includes a slash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-355) offer conversion support for files from jBPM 3 to jBPM 4

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-355?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-355. --------------------------- Resolution: Out of Date > offer conversion support for files from jBPM 3 to jBPM 4 > -------------------------------------------------------- > > Key: GPD-355 > URL: https://issues.jboss.org/browse/GPD-355 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Optional > Fix For: jBPM jPDL Designer 4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
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 September 2016