January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (GPD-246) NullPointerException on Nodes with Action that uses expression

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-246?page=com.atlassian.jira.plugin... ] Koen Aers resolved GPD-246. --------------------------- Fix Version/s: jBPM jPDL Designer 3.1.6 Resolution: Done AFAIK this is fixed. > NullPointerException on Nodes with Action that uses expression > -------------------------------------------------------------- > > Key: GPD-246 > URL: https://jira.jboss.org/jira/browse/GPD-246 > Project: JBoss jBPM GPD > Issue Type: Bug > Environment: Eclipse 3.3 Europa, Kubuntu, java 1.6, Intel core2 duo > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.6 > > > NullpointerException occurs when editing jpdl files that contains nodes with Actions that uses expression. > Sample Test jpdl file > ---------------------------------------------- > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.2" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:jbpm.org:jpdl-3.2 http://jbpm.org/xsd/jpdl-3.2.xsd" > name="NPESample"> > <start-state name="Start"> > <transition to="node1"></transition> > </start-state> > <node name="node1"> > <action name="expression_action" expression="#{handlerBean.handle}"></action> > <transition to="End"></transition> > </node> > <end-state name="End"></end-state> > </process-definition> > ---------------------------------------------- > Stack Trace from eclipse log: > !ENTRY org.eclipse.ui 4 0 2008-06-26 16:06:04.051 > !MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: An unexpected exception was thrown. > !STACK 0 > java.lang.NullPointerException > at org.jbpm.gd.jpdl.xml.EsbNodeMapper.accept(Unknown Source) > at org.jbpm.gd.common.registry.XmlAdapterRegistry.getConfigurationElementByXmlNode(Unknown Source) > at org.jbpm.gd.common.xml.XmlAdapterFactory.createAdapter(Unknown Source) > at org.eclipse.wst.sse.core.internal.provisional.AbstractAdapterFactory.adaptNew(AbstractAdapterFactory.java:120) > at org.eclipse.wst.sse.core.internal.provisional.AbstractAdapterFactory.adapt(AbstractAdapterFactory.java:64) > at org.jbpm.gd.common.xml.XmlAdapterFactory.adapt(Unknown Source) > at org.jbpm.gd.common.xml.XmlAdapter.getAdapter(Unknown Source) > at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source) > at org.jbpm.gd.jpdl.xml.ProcessDefinitionDomAdapter.initialize(Unknown Source) > at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source) > at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source) > at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source) > at org.jbpm.gd.jpdl.editor.JpdlEditor.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.PartPane.setVisible(PartPane.java:299) > at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179) > at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268) > at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) > at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400) > at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) > at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209) > at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604) > at org.eclipse.ui.internal.PartStack.add(PartStack.java:499) > at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) > at org.eclipse.ui.internal.PartStack.add(PartStack.java:485) > at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) > at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) > at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217) > at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207) > at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774) > at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673) > at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2737) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651) > at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643) > at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2565) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603) > at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:286) > at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139) > at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194) > at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244) > at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316) > at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613) > at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.core.runtime.Platform.run(Platform.java:857) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199) > at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818) > at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079) > at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183) > at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263) > at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) > at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) > 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:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) > at org.eclipse.equinox.launcher.Main.run(Main.java:1173) -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-241) jBPM plugin doesn't support default replyTo in ESB Node configuration

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-241?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-241: -------------------------- Component/s: jpdl Fix Version/s: jBPM jPDL Designer 3.1.7 > jBPM plugin doesn't support default replyTo in ESB Node configuration > --------------------------------------------------------------------- > > Key: GPD-241 > URL: https://jira.jboss.org/jira/browse/GPD-241 > Project: JBoss jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.5 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > The jBPM editor in JBoss IDE doesn't support configuration of storing original replyTo message, described here : https://jira.jboss.org/jira/browse/SOA-295 (SOA-295). It's very usefull feature, i'd be glad to have this done without editing xml by hand. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-240) Task reminder is not properly created in xml

by Andrzej Pol (JIRA)

Task reminder is not properly created in xml -------------------------------------------- Key: GPD-240 URL: https://jira.jboss.org/jira/browse/GPD-240 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM jPDL Designer 3.1.3.SP2, jBPM jPDL Designer 3.1.4 Reporter: Andrzej Pol Assignee: Koen Aers -- 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-235) Provide a reliable roadmap

by Thomas Diesler (JIRA)

Provide a reliable roadmap -------------------------- Key: GPD-235 URL: https://jira.jboss.org/jira/browse/GPD-235 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler Assignee: Koen Aers Please provide a reliable roadmap with release dates assigned to each version. -- 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Commented: (GPD-211) Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-211?page=com.atlassian.jira.plugin... ] Koen Aers commented on GPD-211: ------------------------------- Len, is this issue still relevant? > Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503 > ---------------------------------------------------------------------------------------------- > > Key: GPD-211 > URL: https://jira.jboss.org/jira/browse/GPD-211 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: jpdl 3.2.2 - SOA Platform build beta2 > Reporter: Len DiMaggio > Assignee: Koen Aers > > Followup questions on this removal of the XML namespace reference - see SOA-344,JBESB-1503 - in processdefinition.xml files in SOA-P jBPM quickstarts: > http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbossesb/branches/JB... > Was this change made between SOA-P beta1 and beta2 - and if so in response to which JIRA? > Or, was the change in beta1 and we missed it in our testing? > Also - what's the reason for this change? > Another side-effect of this change is that JBDS 1.0 - in creating a new jBPM project - creates a processdefinition file with this (the old) syntax: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.2" > name="simple"> > Should we recommend that users manually remove the namespace reference? -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-211) Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-211?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-211: -------------------------- Component/s: jpdl > Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503 > ---------------------------------------------------------------------------------------------- > > Key: GPD-211 > URL: https://jira.jboss.org/jira/browse/GPD-211 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: jpdl 3.2.2 - SOA Platform build beta2 > Reporter: Len DiMaggio > Assignee: Koen Aers > > Followup questions on this removal of the XML namespace reference - see SOA-344,JBESB-1503 - in processdefinition.xml files in SOA-P jBPM quickstarts: > http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbossesb/branches/JB... > Was this change made between SOA-P beta1 and beta2 - and if so in response to which JIRA? > Or, was the change in beta1 and we missed it in our testing? > Also - what's the reason for this change? > Another side-effect of this change is that JBDS 1.0 - in creating a new jBPM project - creates a processdefinition file with this (the old) syntax: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.2" > name="simple"> > Should we recommend that users manually remove the namespace reference? -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-190) Add policy methods like canStart() and canStop() to NodeElement interface

by Matthias Hanisch (JIRA)

Add policy methods like canStart() and canStop() to NodeElement interface ------------------------------------------------------------------------- Key: GPD-190 URL: http://jira.jboss.com/jira/browse/GPD-190 Project: JBoss jBPM GPD Issue Type: Feature Request Environment: Does not matter Reporter: Matthias Hanisch Assigned To: Koen Aers NodeGraphicalNodeEditPolicy.canStart() method consists of a sum of instanceof checks. Same for canStop(). Especially if you want to create own special nodes, it would be easier if canStart(), canStop() would be implemented by NodeElement interface (there we have the idea of transactions, too). Another policy method which does not exist yet (I just have a use case for that) would be boolean needsNamedTransitions() to specify that a node wants all its leaving transactions to be named. -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1907) Unable to add accumulate functions in Guvnor

by Michael Neale (JIRA)

Unable to add accumulate functions in Guvnor -------------------------------------------- Key: JBRULES-1907 URL: https://jira.jboss.org/jira/browse/JBRULES-1907 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M3 Reporter: Michael Neale Assignee: Michael Neale Fix For: 5.0.0.M5 Should add it so that .properties and .conf files are added automatically to the package configuration for max flexibility. -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (GPD-219) Create installer distribution compatible with eclipse-3.4

by Thomas Diesler (JIRA)

Create installer distribution compatible with eclipse-3.4 --------------------------------------------------------- Key: GPD-219 URL: http://jira.jboss.com/jira/browse/GPD-219 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-79) ProcessDefinitionDomAdapter.NODE_TYPES should not be hardcoded

by John Ruud (JIRA)

ProcessDefinitionDomAdapter.NODE_TYPES should not be hardcoded -------------------------------------------------------------- Key: GPD-79 URL: http://jira.jboss.com/jira/browse/GPD-79 Project: JBoss jBPM GPD Issue Type: Bug Reporter: John Ruud Assigned To: Koen Aers Priority: Blocker I had to add my custom node types to ProcessDefinitionDomAdapter.NODE_TYPES in order to be able to add the nodes from the palette. It would be helpful if ProcessDefinitionDomAdapter.NODE_TYPES could get populated from an extension point instead (similar to: org.jbpm.gd.jpdl.notationMappings). This change is probably already planned, just attempting to bump it up on the priority list slightly as it's something I'm currently using -- 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

17 years, 4 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 January 2009