[JBoss JIRA] Updated: (JBIDE-330) Server view cannot be restored on startup (JBossIDE-200606242318-nightly).
by Bob McWhirter (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-330?page=all ]
Bob McWhirter updated JBIDE-330:
--------------------------------
Assignee: Rob Stryker (was: Robert Stryker)
> Server view cannot be restored on startup (JBossIDE-200606242318-nightly).
> --------------------------------------------------------------------------
>
> Key: JBIDE-330
> URL: http://jira.jboss.com/jira/browse/JBIDE-330
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS Adapter
> Environment: Debian Linux, Kernel 2.6.16, jdk 1.5.0_6-b05, eclipse-SDK-3.2RC7-linux-gtk, JBossIDE-200606242318-nightly
> Reporter: Florian Beckmann
> Assigned To: Rob Stryker
> Fix For: 2.0.0.Alpha
>
>
> Server view cannot be restored on startup. Within the server tab the message "Unable to create view: Argument not valid" is displayed. After closing the tab and reopen it via "Window->showview->Server->JBossServerView." the server view displays fine.
> Error log:
> Message: Unable to create view ID org.jboss.ide.eclipse.as.ui.views.JBossServerView: Argument not valid
> Exception Stack Trace:
> java.lang.IllegalArgumentException: Argument not valid
> at org.eclipse.swt.SWT.error(SWT.java:3358)
> at org.eclipse.swt.SWT.error(SWT.java:3297)
> at org.eclipse.swt.SWT.error(SWT.java:3268)
> at org.eclipse.swt.custom.SashForm.setWeights(SashForm.java:372)
> at org.jboss.ide.eclipse.as.ui.views.JBossServerView.createPartControl(JBossServerView.java:108)
> at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:332)
> at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:197)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:3898)
> at org.eclipse.ui.internal.WorkbenchPage.restoreState(WorkbenchPage.java:2922)
> at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1936)
> at org.eclipse.ui.internal.Workbench.doRestoreState(Workbench.java:2857)
> at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:2805)
> at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1681)
> at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Workbench.java:1421)
> at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1679)
> at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1650)
> at org.eclipse.ui.internal.Workbench$17.run(Workbench.java:1529)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1473)
> at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)
> at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:702)
> at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 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:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
--
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, 11 months
[JBoss JIRA] Updated: (JBIDE-365) Changing hostname in server config (JBoss 'Server Editor'), breaks twiddle monitoring for server startup
by Bob McWhirter (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-365?page=all ]
Bob McWhirter updated JBIDE-365:
--------------------------------
Assignee: Rob Stryker (was: Robert Stryker)
> Changing hostname in server config (JBoss 'Server Editor'), breaks twiddle monitoring for server startup
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-365
> URL: http://jira.jboss.com/jira/browse/JBIDE-365
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS Adapter
> Affects Versions: 2.0.0.Beta1
> Environment: Windows Server 2003
> eclipse-M20060823-1200 (eclipse 3.2)
> JBoss-4.0.4.GA
> jdk1.5.0_06
> Reporter: Johans Marvin Taboada Villca
> Assigned To: Rob Stryker
> Fix For: 2.0.0.Beta3
>
>
> Changing hostname in server config view breaks twiddle monitoring for server startup
> Posible cause, maybe JBossIDE (¿JBossAS Adapter?) access to twiddle script doesn't use yet
> $WORKSPACE\.metadata\.plugins\org.eclipse.wst.server.core\servers.xml
> to set -s option on the twiddle script.
> Also, changing hostname doesn't change Launch configuration, where argument '--host=localhost' is set by default.
> file: $WORKSPACE\.metadata\.plugins\org.eclipse.debug.core\.launches\JBoss-4.0.4.GA.launch
--
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, 11 months
[JBoss JIRA] Commented: (JBIDE-295) Ecllpse 3.2M6 breaks JBossAS adapters...
by Pauline Dumont (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-295?page=comments#action_12362487 ]
Pauline Dumont commented on JBIDE-295:
--------------------------------------
I have the same problem with Eclipse 3.2.2 and latest stable jboss IDE plugin version 1.6.0.
2.0.0 version is still beta and I'd like to keep working with a stable version.
Has someone an idea of how to solve the problem for 1.6.0 version?
> Ecllpse 3.2M6 breaks JBossAS adapters...
> ----------------------------------------
>
> Key: JBIDE-295
> URL: http://jira.jboss.com/jira/browse/JBIDE-295
> Project: JBoss Tools
> Issue Type: Bug
> Affects Versions: 1.5.1
> Reporter: Marshall Culpepper
> Assigned To: Marshall Culpepper
> Fix For: 2.0.0.GA
>
> Attachments: org-jboss-ide-eclipse-launcher-ui.jar
>
>
> The relevant parts of the stack trace:
> java.lang.NoClassDefFoundError:
> org/eclipse/jdt/internal/debug/ui/launcher/JavaLaunchConfigurationTab
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
> ..............
> at
> org.jboss.ide.eclipse.launcher.ui.configuration.jboss.JBoss40xTabGroup.creat
> eTabs(JBoss40xTabGroup.java:60)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfiguration
> Action.performAction(CreateLaunchConfigurationAction.java:70)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurati
> onAction$1.run(AbstractLaunchConfigurationAction.java:103)
> at
> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
> .....
--
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