[JBoss jBPM] - Bug in process designer
by gmournos
The following process taken from testcase Wfp05SimpleMergeTest does not open in the latest version of the process designer.
<?xml version="1.0" encoding="UTF-8"?>
<process-definition>
<start-state name="start">
</start-state>
</process-definition>
Throws:
java.lang.NullPointerException
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addTargetConnection(AbstractGraphicalEditPart.java:261)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refreshTargetConnections(AbstractGraphicalEditPart.java:657)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:556)
at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:212)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198)
at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:727)
at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:677)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:554)
at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:212)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198)
at org.eclipse.gef.editparts.SimpleRootEditPart.setContents(SimpleRootEditPart.java:101)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:583)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:592)
at org.jbpm.ui.editor.DesignerModelViewer.initContents(Unknown Source)
at org.jbpm.ui.editor.DesignerModelViewer.createControl(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.addModelViewer(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.createPartControl(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:183)
at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source)
at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
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:394)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960675#3960675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960675
19 years, 9 months
[JBoss Seam] - Re: Avoiding the DRY Principle with beans
by bfo81
1) Yes, that's what I found out, too. Thanks ;).
4) Sounds good. At the end of each edit page I have something like
anonymous wrote : <h:commandButton value="Save" action="#{whateverentityEditor.save}" />
| <h:commandButton value="Delete" action="#{whateverentityEditor.delete}" immediate="true" rendered="#{not whateverentityEditor.newOne}" />
| <h:commandButton value="Cancel" action="#{whateverentityEditor.cancel}" immediate="true" />
It would be quite nice to have it like that:
anonymous wrote : <xyz:showEditButtons value="whateverentityEditor" />
Even the list page could get more decorated, so that I only need to enter the columns shown. The surrounding dataTable-Tags, the "edit item" buttons, the "create new" button, and even the "No items found" or other messages shouldn't be typed in by the developer explicitly.
Well, there's a lot of work to do for me. I already have a working list/edit example, but there are so many more ideas. Pagination on the list page is another thing I haven't built in yet.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960673#3960673
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960673
19 years, 9 months