February 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3759) Servers properties menu errors.

by Aliaksey Nis (JIRA)

Servers properties menu errors. ------------------------------- Key: JBIDE-3759 URL: https://jira.jboss.org/jira/browse/JBIDE-3759 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Environment: WindowsXP SP2 JBoss Developer Studio Version: 2.0.0.GA Build id: jbdevstudio-eap-win32-2.0.0.GA-N200902040901-H1418 JRE 1.5_08 Reporter: Aliaksey Nis Fix For: 3.0.0.GA Attachments: serverProp.txt, serversproperties.JPG Part1. EXECUTE: Newly installed studio. Server runtimes added during installation. EXECUTE: Open Servers view. EXECUTE: Right click on any server(Jboss 4.2.3 for example). Select Properties > General. EXECUTE: Press "Switch location button". ASSERT: Location switched. From Workspace metadata to target folder. ASSERT: Folder Servers appears in Package Explorer(and in filsystem) with server settings inside. EXECUTE: New > Seam Project > Create any Seam project. FAILURE: Exceptions related to JBoss AS server thrown in error log. Error log attached. Project cannot be started on server (deployment errors). Part2 EXECUTE: Double click on server in Servers view. ASSERT: Server settings appears. EXECUTE: Right click on this server in server view. Select properties. Press "Switch location" button(from workspace metadata to target folder). ASSERT: Location changed. EXECUTE: Press Ok in properties menu. EXECUTE: In server settings make some changes(check another checkbox for deploy option for example). Try to save those changes. FAILURE: Error mesage box appears and exceptions w/o stacktrace thrown in error log. Properties wizard don't check ,if server settings files used but any other wizard. Screenshot attached. -- 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, 1 month

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3809) Error saving server editor when the file has been modified since the start of editing.

by Anton Klimkovich (JIRA)

Error saving server editor when the file has been modified since the start of editing. -------------------------------------------------------------------------------------- Key: JBIDE-3809 URL: https://jira.jboss.org/jira/browse/JBIDE-3809 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich EXECUTE: Double click on server in Servers view. ASSERT: Server Overview wizard appeares. EXECUTE: Swith radiobutton to Use custom deploy folder. EXECUTE: Right click on this server in server view. Select properties. Press "Switch location" button(from workspace metadata to target folder) EXECUTE: Back to Server Overview wizard ASSERT: Suggestion to save file. EXECUTE: Select Do not save the changes. EXECUTE: Save file using Ctrl+S or Save icon FAILURE: Error saving server editor. Log attached. Maybe related to JBIDE-3759 -- 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, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3024) Unhandled event loop exception when create additional struts-configuration file.

by Anton Klimkovich (JIRA)

Unhandled event loop exception when create additional struts-configuration file. -------------------------------------------------------------------------------- Key: JBIDE-3024 URL: https://jira.jboss.org/jira/browse/JBIDE-3024 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Attachments: exception.txt EXECUTE: Create Struts KickStart project EXECUTE: New -> Struts Config EXECUTE: Set version 1.2 and press Finish button FAILURE: Unhandled event loop exception . -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3615) OpenOn doesn't work on for f:loadBundle var="resources" in specific way.

by Anton Klimkovich (JIRA)

OpenOn doesn't work on for f:loadBundle var="resources" in specific way. ------------------------------------------------------------------------ Key: JBIDE-3615 URL: https://jira.jboss.org/jira/browse/JBIDE-3615 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.CR2 Reporter: Anton Klimkovich Assignee: Victor Rubezhny Fix For: 3.0.0.GA EXECUTE: Create JsfwithFacelets project EXECUTE: In pages folder create any .Xhtml page with FaceletForm template EXECUTE: Add <f:loadBundle var="resources" basename="msg"/> to the page EXECUTE: Try OpenOn on resources. FAILURE: OpenOn doesn't work. EXECUTE: Add #{msg.prompt} and try OpenOn on it FAILURE: OpenOn doesn't work. If you try to make such OpenOn on greeting.xhtml it will work fine. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3826) Color parameter of style attribute in rich:dataTable shouldn't be applied for facets of rich:columns

by Yura Zhishko (JIRA)

Color parameter of style attribute in rich:dataTable shouldn't be applied for facets of rich:columns ---------------------------------------------------------------------------------------------------- Key: JBIDE-3826 URL: https://jira.jboss.org/jira/browse/JBIDE-3826 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.GA Reporter: Yura Zhishko Assignee: Yahor Radtsevich Priority: Minor -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-465) Docs building instruction

by Svetlana mukhina (JIRA)

Docs building instruction -------------------------- Key: JBDS-465 URL: https://jira.jboss.org/jira/browse/JBDS-465 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Michael Sorokin Fix For: 2.0.0.beta1 It's necessary to write docs building instruction -- 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, 1 month

3
18
0 / 0

[JBoss JIRA] Created: (JBDS-496) Splash screen has wrong version when run JBDS.

by Anton Klimkovich (JIRA)

Splash screen has wrong version when run JBDS. ---------------------------------------------- Key: JBDS-496 URL: https://jira.jboss.org/jira/browse/JBDS-496 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.0.cr1 Reporter: Anton Klimkovich Attachments: Splash screen after run.PNG Version of JBDS should be 2.0.0CR1 instead of 2.0.0beta1 -- 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, 1 month

6
25
0 / 0

[JBoss JIRA] Created: (JBIDE-3824) SWT Exception Occurs in JBossAS New Server Wizard Fragment

by Denis Golovin (JIRA)

SWT Exception Occurs in JBossAS New Server Wizard Fragment ---------------------------------------------------------- Key: JBIDE-3824 URL: https://jira.jboss.org/jira/browse/JBIDE-3824 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Rob Stryker Fix For: 3.0.0.GA use test in org.jboss.ide.eclipse.as.ui.test plug-in to reproduce the error junit.framework.AssertionFailedError: Unhandled event loop exception during blocked modal context. org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.performFinish(TaskWizard.java:221) at org.jboss.ide.as.ui.test.NewServerWizardTest.testJbide(NewServerWizardTest.java:114) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:114) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:46) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.SWT.error(SWT.java:3666) at org.eclipse.swt.widgets.Widget.error(Widget.java:446) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:384) at org.eclipse.swt.widgets.Text.setText(Text.java:1893) at org.jboss.ide.eclipse.as.ui.wizards.JBossServerWizardFragment.enter(JBossServerWizardFragment.java:251) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard$2$1.run(TaskWizard.java:175) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:155) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) ... 52 more at junit.framework.Assert.fail(Assert.java:47) at org.jboss.ide.as.ui.test.NewServerWizardTest.logging(NewServerWizardTest.java:128) at org.eclipse.core.internal.runtime.RuntimeLog.log(RuntimeLog.java:95) at org.eclipse.core.internal.runtime.InternalPlatform.log(InternalPlatform.java:669) at org.eclipse.core.internal.runtime.Log.log(Log.java:56) at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:861) at org.eclipse.ui.statushandlers.StatusManager.logError(StatusManager.java:298) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:213) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:244) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:255) at org.eclipse.ui.internal.JFaceUtil$2.log(JFaceUtil.java:58) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:204) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.performFinish(TaskWizard.java:221) at org.jboss.ide.as.ui.test.NewServerWizardTest.testJbide(NewServerWizardTest.java:114) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:114) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:46) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-623) Snooks editor: configuration page

by Svetlana mukhina (JIRA)

Snooks editor: configuration page ---------------------------------- Key: JBDS-623 URL: https://jira.jboss.org/jira/browse/JBDS-623 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.cr2 Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.0.0.GA Smooks guide: new page of editor should be describe, it's used to edit/add/remove "import" type. see the linked task -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-578) Open Web Browser toolbar action is added to the Seam perspective

by Svetlana mukhina (JIRA)

Open Web Browser toolbar action is added to the Seam perspective ---------------------------------------------------------------- Key: JBDS-578 URL: https://jira.jboss.org/jira/browse/JBDS-578 Project: Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 2.0.0.cr1 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.GA tell in the guide that The Open Web Browser action is now directly available in the Seam perspective, make a screen of it. see the linked issue for details and what's ne corresponding section - http://docs.jboss.org/tools/whatsnew/seam/seam-news-2.0.0.CR1.html -- 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, 1 month

2
1
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 February 2009