June 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3618) jPDL designer loses changes and cannot edit file anymore

by Hedley Proctor (JIRA)

jPDL designer loses changes and cannot edit file anymore -------------------------------------------------------- Key: JBIDE-3618 URL: https://jira.jboss.org/jira/browse/JBIDE-3618 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: LATER Environment: Windows xp 32-bit Reporter: Hedley Proctor I've created a number of workflows using the Eclipse jPDL designer. Yesterday I created a fourth workflow by copying a previous one. After about an hours work, I had added another 10 states to the workflow. I saved it and shutdown Eclipse. Now I have opened Eclipse and none of the changes to the workflow have been saved. The Eclipse local history shows the last file version available as 17:22 yesterday, whereas in fact I worked until about 18:30. Also, the file that remains is corrupt. It has transitions into and out of a state that doesn't exist. When I try to delete the transition in, in is deleted from the file, but it still remains on the graphical view. The Eclipse log shows a DOM parsing error: org.w3c.dom.DOMException: at org.eclipse.wst.xml.core.internal.document.NodeContainer.removeChild(NodeContainer.java:371) at org.jbpm.gd.common.xml.XmlAdapter.removeElement(Unknown Source) at org.jbpm.gd.common.xml.XmlAdapter.removeElement(Unknown Source) at org.jbpm.gd.jpdl.xml.StartStateDomAdapter.doPropertyChange(Unknown Source) at org.jbpm.gd.common.xml.XmlAdapter.propertyChange(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at org.jbpm.gd.common.model.AbstractSemanticElement.firePropertyChange(Unknown Source) at org.jbpm.gd.jpdl.model.AbstractNode.removeTransition(Unknown Source) at org.jbpm.gd.jpdl.command.EdgeDeleteCommand.execute(Unknown Source) at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:107) at org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:149) at org.eclipse.gef.ui.actions.WorkbenchPartAction.execute(WorkbenchPartAction.java:76) at org.eclipse.gef.ui.actions.DeleteAction.run(DeleteAction.java:125) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) 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: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(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:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) Eclipse version: 3.3.2 M20080221-1800 jPDL designer version: 3.1.3 SP2 -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3611) Saving jBPM Project clears out "Java Classes and Resources" settings in jBPM deployment tab

by Aaron Pestel (JIRA)

Saving jBPM Project clears out "Java Classes and Resources" settings in jBPM deployment tab ------------------------------------------------------------------------------------------- Key: JBIDE-3611 URL: https://jira.jboss.org/jira/browse/JBIDE-3611 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Environment: JBoss Developer Studio Version: 2.0.0.CR1 Build id: R200812221144 Build date: 12/22/2008 11:54 Reporter: Aaron Pestel Priority: Minor Maybe this is a feature request, but I would tend to call it a bug. When deploying a jBPM project from JBDS, you click on the deployment tab of the jBPM process editor. If there are any Java files in your jBPM project (like a custom jBPM action), you have to select the "src/main/Java" checkbox in the "Java Classes and Resources Panel" or the Java class will not be deployed to the server when you deploy the jBPM process and you'll get class not found exceptions when you run the jBPM process. That's all fine. What is annoying is that every time you save the jBPM project, it automatically unselects all the checkboxes in the "Java Classes and Resources Panel". So, if you don't recheck that "src/main/Java" checkbox every time you save the jBPM project (which is pretty much every time you change the project), then you'll end up deploying the jBPM project without the necessary custom Java actions. I'm requesting that the check boxes not be reset every time the jBPM project is saved. It looks like saving the jBPM project also resets all "Files and Folders" panel of the jBPM deployment tab. i wouldn't think anything should be reset when the project is saved. -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3489) source editor breaks XML when undoing

by Nick Boldt (JIRA)

source editor breaks XML when undoing ------------------------------------- Key: JBIDE-3489 URL: https://jira.jboss.org/jira/browse/JBIDE-3489 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.cr1 Reporter: Nick Boldt Tested with JBoss Dev Studio Version: 2.0.0.CR1, Build id: R200812221144 Steps to repro: 1. Install JBDS. 2. download http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://download... 3. `java -jar jbpm-installer-3.3.0.GA.jar`. I installed into ~/jbpm-3.3.0.GA 4. New > Other > Process Project 5. Go into src/main/jpdl/simple and open processdefinition.xml with jBPM Graphical Process Designer 6. Add a couple nodes, then connect them to the existing flow. 7. Switch to Source tab. I had this: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="simple"> <start-state name="start"> <transition name="to_state" to="first"> <action name="action" class="com.sample.action.MessageActionHandler"> <message>Going to the first state!</message> </action> </transition> <transition to="mail-node1" name="to mail-node1"></transition> </start-state> <state name="first"> <transition name="to_end" to="end"> <action name="action" class="com.sample.action.MessageActionHandler"> <message>About to finish!</message> </action> </transition> </state> <task-node name="task-node1"> <transition to="end"></transition> </task-node> <mail-node name="mail-node1"> <transition to="task-node1"></transition> </mail-node> <end-state name="end"></end-state> </process-definition> 8. Select the name of some node, eg., "mail-node1". Hit delete. Cursor jumps here: <mail-node name=""> <tran|sition to="task-node1"></transition> </mail-node> 9. CTRL-Z to undo change(s). Now I get this: <mail-node name=""> <tranmail-node1sition to="task-node1"></transition> </mail-node> 10. Save. Close. Reopen. Diagram is now in a broken state, with a Transition pointing into space, and the Mail Node no longer coupled to anything. 11. Switch to source view again. Paste the correct text from step 7 into the editor. Close. Reopen. The UI layout in the Diagram view is corrupt, with nodes all moved to the 0,0 coord corner (top left). 12. Switch to the source view. Select the name of the task-node, and change it. Undo w/ CTRL-Z. Continue undoing, and watch as the XML gets corrupted to this: <task-node name="task-node1"> <transition to="end"></transition> </task-node> <mail-node name="mail-node1"> <trans"task-node1"on to=""a"</transition> </mail-node> -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3490) dirty jBPM Graphical Process Designer editor saves layout changes without prompting user or loses changes if gpd.xml is open to Source tab

by Nick Boldt (JIRA)

dirty jBPM Graphical Process Designer editor saves layout changes without prompting user or loses changes if gpd.xml is open to Source tab ------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-3490 URL: https://jira.jboss.org/jira/browse/JBIDE-3490 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.cr1 Reporter: Nick Boldt Tested with JBoss Dev Studio Version: 2.0.0.CR1, Build id: R200812221144 Steps to repro: 1. Install JBDS. 2. download http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://download... 3. `java -jar jbpm-installer-3.3.0.GA.jar`. I installed into ~/jbpm-3.3.0.GA 4. New > Other > Process Project 5. Go into src/main/jpdl/simple and open processdefinition.xml with jBPM Graphical Process Designer 6. Add a couple nodes, then connect them to the existing flow. 7. Switch to Source tab. I had this: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="simple"> <start-state name="start"> <transition name="to_state" to="first"> <action name="action" class="com.sample.action.MessageActionHandler"> <message>Going to the first state!</message> </action> </transition> <transition to="mail-node1" name="to mail-node1"></transition> </start-state> <state name="first"> <transition name="to_end" to="end"> <action name="action" class="com.sample.action.MessageActionHandler"> <message>About to finish!</message> </action> </transition> </state> <task-node name="task-node1"> <transition to="end"></transition> </task-node> <mail-node name="mail-node1"> <transition to="task-node1"></transition> </mail-node> <end-state name="end"></end-state> </process-definition> 8. Click [x] on editor tab to close it. You should be prompted to save dirty editor. Save. 9. Reopen editor. Move some nodes around. Note editor is again in 'dirty' state. 10. Click [x] on editor tab to close it. This time you're not prompted to save (because the changes are in a different file, gpd.xml). 11. Repeat steps 9-10, verifying that changes to layout are saved into gpd.xml. ** Surely these changes to UI layout shouldn't be automatically written without the user's confirmation? ** -- 11. Open gpd.xml using xml editor. Switch to Source tab and note (x,y) coords for the start node. 12. Reopen processdefinition.xml in jBPM Graphical Process Designer editor. Move the start node. Note editor is again in 'dirty' state, as in step 9 above. 13. Click [x] on editor tab to close it. Still not prompted, as in step 10. Close gpd.xml too. 14. Reopen gpd.xml. This time, nothing has changed! ** Surely layout changes shouldn't just vanish if the gpd.xml file's open in parallel with the jBPM Graphical Process Designer editor? ** -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4254) Prevent diagram nodes from overlapping

by Nick Boldt (JIRA)

Prevent diagram nodes from overlapping -------------------------------------- Key: JBIDE-4254 URL: https://jira.jboss.org/jira/browse/JBIDE-4254 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.GA Reporter: Nick Boldt Steps to repro: 1. Using JBDS 2.0.0.GA and jbpm 3.3.0.GA, create a new Process Project. 2. Open /<project>/src/main/jpdl/simple/processdefinition.xml 3. Add a new State node. 4. Drag it on top/under the existing (generated) State node. Resize it as necessary until they overlap perfectly. Compare to JBPM Editor 1.0.2 from SOA Tools project @ Eclipse.org. 1. Using Eclipse 3.4.2 and BPMN Editor 1.0.2 (http://download.eclipse.org/stp/bpmn-modeler/1.0.2/updates/), create an empty project. 2. Create a new Bpmn Diagram (under "Other" group). 3. Create some nodes. 4. When you try to drop a node onto another one, the overlapping area turns red to indicate you cannot overlap them. If you release while in this red state, the node returns to its previous location. In other words, you are prevented from overlapping nodes - only transition lines can overlap. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3916) Open CSS Class Dialog on css file from Package Explorer.

by Denis Maliarevich (JIRA)

Open CSS Class Dialog on css file from Package Explorer. -------------------------------------------------------- Key: JBIDE-3916 URL: https://jira.jboss.org/jira/browse/JBIDE-3916 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Denis Maliarevich Assignee: Maxim Areshkau Fix For: 3.1.0 Steps to reproduce: 1. Select any css file in Package Explorer by mouse click. 2. Notice that there is no CSS Class Dialog icon in the toolbar. 3. Right click on selected css file -> Popup menu will appear with "Open CSS Dialog" menu item. The problem is in the mismatch between icon presence and menu item presence. If there is a menu item than there also should be a toolbar icon to open CSS Class Dialog. -- 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, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBDS-374) hotkey methods for project archiver description

by Svetlana mukhina (JIRA)

hotkey methods for project archiver description ----------------------------------------------- Key: JBDS-374 URL: http://jira.jboss.com/jira/browse/JBDS-374 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: OLga Chikvina Fix For: 2.0.0.alpha describe new hotkey methods for project archiver -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-386) ESB Editor is Extended

by Svetlana mukhina (JIRA)

ESB Editor is Extended ---------------------- Key: JBDS-386 URL: https://jira.jboss.org/jira/browse/JBDS-386 Project: Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.alpha Update the guide according to https://jira.jboss.org/jira/browse/JBIDE-2022 -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-731) Wikipedia articles on Tools and JBDS

by Svetlana mukhina (JIRA)

Wikipedia articles on Tools and JBDS ------------------------------------ Key: JBDS-731 URL: https://jira.jboss.org/jira/browse/JBDS-731 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Michael Sorokin Fix For: 2.0.1 It's necessary to update the following articles: http://en.wikipedia.org/wiki/JBoss_Tools http://en.wikipedia.org/wiki/JBDS -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4136) Use recommended packaging for Seam EAR projects

by Pete Muir (JIRA)

Use recommended packaging for Seam EAR projects ----------------------------------------------- Key: JBIDE-4136 URL: https://jira.jboss.org/jira/browse/JBIDE-4136 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Pete Muir Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.0.1.GA JBT uses MANIFEST.MF for setting up artifact classpath, whilst Seam recommends the use of the EAR lib/ directory. By not following this recommendation, JBT users are running in to a number of classloading problems. -- 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, 6 months

4
28
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2009