[JBoss JIRA] Created: (JBIDE-3088) BPMN -> jPDL wizard fails if selected file is not BPMN
by John Graham (JIRA)
BPMN -> jPDL wizard fails if selected file is not BPMN
------------------------------------------------------
Key: JBIDE-3088
URL: https://jira.jboss.org/jira/browse/JBIDE-3088
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.0.0.beta1
Environment: JBT 3.0 beta 1 build
Reporter: John Graham
Assignee: Feng Qian
Priority: Critical
Fix For: 3.0.0.cr1
If the resource (file/folder/project) selected when the BPMN -> jPDL wizard is launched is not a BPMN file, then the wizard does not open, failing with the exception below. Since the user selects the BPMN resource(s) to convert on the first page of the wizard, it should not matter what the current selection is when the wizard starts:
eclipse.buildId=M20080911-1700
java.version=1.6.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -clean
Error
Fri Oct 31 13:48:56 GMT-05:00 2008
Unhandled event loop exception
java.lang.NullPointerException
at org.jboss.tools.jbpm.convert.bpmnto.wizard.BpmnPoolsChoicePage.initializeViewer(BpmnPoolsChoicePage.java:163)
at org.jboss.tools.jbpm.convert.bpmnto.wizard.BpmnPoolsChoicePage.createControl(BpmnPoolsChoicePage.java:67)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:669)
at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1083)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1142)
at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1139)
at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1128)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1126)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:820)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:97)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:116)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
--
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, 5 months
[JBoss JIRA] Created: (JBIDE-2657) Server view to remember property expansion
by Galder Zamarreno (JIRA)
Server view to remember property expansion
------------------------------------------
Key: JBIDE-2657
URL: https://jira.jboss.org/jira/browse/JBIDE-2657
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Galder Zamarreno
Whenever you click on a server in the server view, another
window opens listing the modules, event log...etc. If I expand
the modules or event log, then switch to a different server and
switch back again, different trees are collapsed again. This
can be a pain when dealing with multiple servers at the same,
i.e.cluster.
It'd be nice if when switching to a different server, it could
remember the status of the different modules, event trees so
that if you click back, everything is like it was before.
Thoughts?
--
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, 5 months
[JBoss JIRA] Updated: (JBIDE-1226) Various bugs in visual previews of richfaces components
by Maxim Areshkau (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-1226?page=com.atlassian.jira.plu... ]
Maxim Areshkau updated JBIDE-1226:
----------------------------------
Fix Version/s: LATER
(was: 3.0.0.cr1)
> Various bugs in visual previews of richfaces components
> -------------------------------------------------------
>
> Key: JBIDE-1226
> URL: https://jira.jboss.org/jira/browse/JBIDE-1226
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor Templates
> Reporter: Gavin King
> Assignee: Maxim Areshkau
> Fix For: LATER
>
> Attachments: calendar.png, calendar_ve.png, dataDefinitionList.png, dataDefinitionList_ve.png, dataTable.png, dataTable_ve.png, dropDownMenu.png, dropDownMenu_ve.png, inputNumberSlider.png, inputNumberSlider_ve.png, modalPanel.png, modalPanel_ve.png, panelBar.png, panelBar_ve.png, panelMenu.png, panelMenu_ve.png, status.png, status_ve.png, toolTip.png, toolTip_ve.png, tree.png, tree_ve.png
>
>
> Here's a list of previews that need fixing:
> rich:calendar won't popup, and puts the button in the wrong place
> rich:dataDefinitionList broken
> rich:dropDownMenu nonfunctional
> rich:panelMenu nonfunctional
> rich:panelBar functional, but rendering is broken
> rich:toolTip nonfunctional
> rich:modalPanel nonfunctional
> rich:dataTable broken
> rich:tree sorta works, but the nodes are not functional and don't render as links
> rich:inputNumberSlider and other sliders are ugly
> a4j:status should show some kind of preview
--
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, 5 months
[JBoss JIRA] Created: (JBIDE-3100) Project Archives option should be smart enough to ignore .svn/cvs folders by default
by Francisco Jose Peredo Noguez (JIRA)
Project Archives option should be smart enough to ignore .svn/cvs folders by default
------------------------------------------------------------------------------------
Key: JBIDE-3100
URL: https://jira.jboss.org/jira/browse/JBIDE-3100
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
Project Archives feature should be smart enough to ignore .svn/cvs folders by default, but it is not, therefore if I try to generate a WAR for my project with it, it creates it with copies of the .svn folders inside it, this make it huge, takes the processor to 50% an leaves it there forever. To make things worse, there is no way to stop the process, so all I can do is kill eclipse.
But the problem does not stop then, because after I restart, the incomplete build processes that I killed starts again, and I have kill eclipse again, and revert my project configuration files to the state before I tried to use the Project Archives feature.
--
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, 5 months
[JBoss JIRA] Created: (JBIDE-2860) Incorrect connection of CSS
by Andrei Scherbovich (JIRA)
Incorrect connection of CSS
---------------------------
Key: JBIDE-2860
URL: https://jira.jboss.org/jira/browse/JBIDE-2860
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 3.0.0.alpha
Reporter: Andrei Scherbovich
Assignee: Dzmitry Sakovich
1) If we try to describe styles in different CSS for the same tag, for example <body>, with using the same param, for example "color", but with the different values, for example "red" in first CSS, "blue" in other. And if we use <link> proccedures fot the both CSS files without setting up these files in Page Designe Options, we will see different results. The same style with the same param but with the different value is used from the first <link>, but it have to be used from last <link>, as browsers do.
2) Now include these pages in Page Designe Options. VPE read style only from the first including, independently of <link> processing
--
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, 5 months