January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-34) Review the extension points and mechanism.

by Koen Aers (JIRA)

Review the extension points and mechanism. ------------------------------------------ Key: GPD-34 URL: http://jira.jboss.com/jira/browse/GPD-34 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl 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

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-143) Load the icon of a paletteContribution entry from the plugin directory where it is defined

by Matthias Hanisch (JIRA)

Load the icon of a paletteContribution entry from the plugin directory where it is defined ------------------------------------------------------------------------------------------ Key: GPD-143 URL: http://jira.jboss.com/jira/browse/GPD-143 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Matthias Hanisch Assigned To: Koen Aers In PaletteRoot class, the icon of a palette entry is always loaded from org.jbpm.gd.jpdl plugin, even if the paletteContribution entry is defined in a dependent plugin. The information, where the palette entry element (entryElement in PaletteRoot.addControls) is defined, can be found in entryElement.getContributor().getName(). So also the corresponding image can be loaded from the correct bundle. [ Sorry to only give a verbal description of the implementation. I would sign a corporate contributor's agreement, but I have problems with the procedure, e.g. - do we need a corporate jboss account for my boss to sign - if we sign with the "corporate" account, with which account I need to contribute then etc. So I would need some assistance here. Then you would get a real diff also. ] -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (GPD-171) Split the jPDL plugin in a Common/jPDL/BPEL plugin triad

by Koen Aers (JIRA)

Split the jPDL plugin in a Common/jPDL/BPEL plugin triad -------------------------------------------------------- Key: GPD-171 URL: http://jira.jboss.com/jira/browse/GPD-171 Project: JBoss jBPM GPD Issue Type: Task Reporter: Koen Aers Assigned To: Koen Aers the common classes and extension points have to be included in the common plugin -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-172) Develop an extension example for a simple DSL in its own plugin

by Koen Aers (JIRA)

Develop an extension example for a simple DSL in its own plugin --------------------------------------------------------------- Key: GPD-172 URL: http://jira.jboss.com/jira/browse/GPD-172 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

17 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-178) ClassCastException using Process Designer 3.1.0SP1

by Ian Priest (JIRA)

ClassCastException using Process Designer 3.1.0SP1 -------------------------------------------------- Key: GPD-178 URL: http://jira.jboss.com/jira/browse/GPD-178 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.0.SP1 Environment: Windows XP, Java 1.6.0_02, Eclipse 3.3, suite_3.2.2 (which packages GPD 3.1.0SP1) Reporter: Ian Priest Assigned To: Koen Aers Get a ClassCastException using the Process Designer to open the gpd.xml in the websales example provided with the 3.2.2 suite download. The exception is (full stack trace to follow) java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement The problem seems to lie in class GenericElementXmlAdapter, which deals with the classes though the SemanticElement interface, which both classes do implement. The following class reproduces the runtime issue and demonstrates the faulty cast: import org.jbpm.gd.common.model.GenericElement; import org.jbpm.gd.common.model.SemanticElement; import org.jbpm.gd.jpdl.model.ProcessDefinition; public class Play { public static void main(String[] args) { ProcessDefinition pd = new ProcessDefinition(); SemanticElement se = (SemanticElement)pd; GenericElement ge = (GenericElement)se; } } which gives a runtime error: Exception in thread "main" java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement at Play.main(Play.java:15) See also the forum discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121355 Full stack trace: !ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685 !MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement !STACK 0 java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement at org.jbpm.gd.common.xml.GenericElementXmlAdapter.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:2719) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328) at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) 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:153) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (GPD-180) Problems with delete of start state

by Koen Aers (JIRA)

Problems with delete of start state ----------------------------------- Key: GPD-180 URL: http://jira.jboss.com/jira/browse/GPD-180 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM jPDL Designer 3.1.0.SP1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM jPDL Designer 3.1.1 -- 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, 6 months

1
6
0 / 0

[JBoss JIRA] Resolved: (GPD-194) CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-194?page=com.atlassian.jira.plugin... ] Koen Aers resolved GPD-194. --------------------------- Resolution: Done > CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD > -------------------------------------------------------------- > > Key: GPD-194 > URL: https://jira.jboss.org/jira/browse/GPD-194 > Project: JBoss jBPM GPD > Issue Type: Bug > Affects Versions: jBPM jPDL Designer 3.1.1 > Environment: JBoss Developer Studio, Build id: 200712091205-nightly > and > Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > Reporter: Koen Aers > Assignee: Koen Aers > > I'm unable to generate a new form for a task with either the 1.0 JBDS bits or Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > To recreate the problem - using the attached jBPM process project - it's based on the 'holiday request' jBPM demo - at the start task node, attempt to generate a form. > The screen displayed in the screenshot attachment is brought up - pressing OK has no effect. The form xhtml file is not created - and no error/sttaus message is displayed. > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (GPD-194) CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-194?page=com.atlassian.jira.plugin... ] Koen Aers reopened GPD-194: --------------------------- > CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD > -------------------------------------------------------------- > > Key: GPD-194 > URL: https://jira.jboss.org/jira/browse/GPD-194 > Project: JBoss jBPM GPD > Issue Type: Bug > Affects Versions: jBPM jPDL Designer 3.1.1 > Environment: JBoss Developer Studio, Build id: 200712091205-nightly > and > Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.2 > > > I'm unable to generate a new form for a task with either the 1.0 JBDS bits or Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > To recreate the problem - using the attached jBPM process project - it's based on the 'holiday request' jBPM demo - at the start task node, attempt to generate a form. > The screen displayed in the screenshot attachment is brought up - pressing OK has no effect. The form xhtml file is not created - and no error/sttaus message is displayed. > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-194) CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-194?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-194: -------------------------- Fix Version/s: (was: jBPM jPDL Designer 3.2.0.alpha1) > CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD > -------------------------------------------------------------- > > Key: GPD-194 > URL: https://jira.jboss.org/jira/browse/GPD-194 > Project: JBoss jBPM GPD > Issue Type: Bug > Affects Versions: jBPM jPDL Designer 3.1.1 > Environment: JBoss Developer Studio, Build id: 200712091205-nightly > and > Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.2 > > > I'm unable to generate a new form for a task with either the 1.0 JBDS bits or Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 > To recreate the problem - using the attached jBPM process project - it's based on the 'holiday request' jBPM demo - at the start task node, attempt to generate a form. > The screen displayed in the screenshot attachment is brought up - pressing OK has no effect. The form xhtml file is not created - and no error/sttaus message is displayed. > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-195) sub-process name not loaded

by Wojtas Koziej (JIRA)

sub-process name not loaded --------------------------- Key: GPD-195 URL: http://jira.jboss.com/jira/browse/GPD-195 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM jPDL Designer 3.1.2 Environment: Eclipse 3.3.0 Reporter: Wojtas Koziej Assigned To: Koen Aers I load process definiotion file (below), click process-state node, open properties view, click subprocess tab and there is no sub-process name in the Subprocess Name field. When I change the value of Subprocess Name field and want to save file nothing hapens (Source is not sync). <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="testsub"> <start-state name="start-state1"> <transition to="process-state1"></transition> </start-state> <process-state name="process-state1"> <sub-process name="test-name"/> <transition to="end-state1"></transition> </process-state> <end-state name="end-state1"></end-state> </process-definition> -- 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, 6 months

2
6
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