[JBoss JIRA] (JBIDE-19699) jpa new entity: java.lang.IllegalArgumentException
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19699:
----------------------------------
Summary: jpa new entity: java.lang.IllegalArgumentException
Key: JBIDE-19699
URL: https://issues.jboss.org/browse/JBIDE-19699
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.3.0.Alpha2
Environment: forge 2.16.0
Reporter: Pavol Srna
Fix For: 4.3.0.Beta1
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException)
at org.eclipse.swt.SWT.error(SWT.java:4481)
at org.eclipse.swt.SWT.error(SWT.java:4396)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:210)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:233)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:343)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1504)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1634)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1600)
at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5757)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908)
at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085)
at org.eclipse.swt.widgets.Control.keyDown(Control.java:2406)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5667)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5729)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5166)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5315)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
Caused by: java.lang.IllegalArgumentException
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:1938)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:521)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:56)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:192)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:99)
at sun.reflect.GeneratedMethodAccessor319.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.isEnabled(AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.java)
at sun.reflect.GeneratedMethodAccessor325.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.isEnabled(AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.java)
at org.jboss.tools.forge.ui.internal.ext.control.ControlBuilder.updateState(ControlBuilder.java:192)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.updatePageState(ForgeWizardPage.java:203)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.validatePage(ForgeWizardPage.java:237)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.access$5(ForgeWizardPage.java:233)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage$1$1.run(ForgeWizardPage.java:180)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
... 60 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15884:
-------------------------------------
[~maxandersen], do you mean 2 commands (with and without vpe prefix) ? yes we can keep both them but the commands will be duplicated in Quick Access I think.
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19654:
----------------------------------------
Assignee: Andre Dietisheim (was: Marián Labuda)
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19654:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19654:
------------------------------------------
[~mlabuda] ok, thx for verifying. I'll try to look into the code and see if it's possible that the application wizard would not react to timeouting ssh jobs and open up in an invalid state like it is shown in the above screenshot.
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years