November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7251) Remote launcher should verify if server is up or not

by Rob Stryker (JIRA)

Remote launcher should verify if server is up or not ---------------------------------------------------- Key: JBIDE-7251 URL: https://jira.jboss.org/browse/JBIDE-7251 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M2 Environment: If a remote server is already up, the as-tools rse methods will try to launch a new one without recognizing it's already started Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7265) EL refactoring is too slow.

by Alexey Kazakov (JIRA)

EL refactoring is too slow. --------------------------- Key: JBIDE-7265 URL: https://jira.jboss.org/browse/JBIDE-7265 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 I have a test project with more than 140 000 ELs. And it takes ~ 10 minutes to rename a method name using Java refactoring dialog even if this java class is not used in ELs at all. The reason of it is that we check every EL in the project when a user tries to refactor a java class. As a temporary solution we can use ValidationContext to get relevant ELs only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7147) Validation performance: creating problem markers takes a long time.

by Alexey Kazakov (JIRA)

Validation performance: creating problem markers takes a long time. ------------------------------------------------------------------- Key: JBIDE-7147 URL: https://jira.jboss.org/browse/JBIDE-7147 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 Our validators create a marker for every problem. But if there are a lot of problems then it decreases performance dramatically. We should limit the number of markers for a resource. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7152) org.jboss.tools.jsf.test fails

by Alexey Kazakov (JIRA)

org.jboss.tools.jsf.test fails ------------------------------ Key: JBIDE-7152 URL: https://jira.jboss.org/browse/JBIDE-7152 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 Failed tests: testELVariableRename(org.jboss.tools.jsf.test.refactoring.ELVariableRefactoringTest) testMessagePropertyRename(org.jboss.tools.jsf.test.refactoring.MessagePropertyRefactoringTest) testMoveCompositeComponentFile(org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest) testMoveCompositeComponentFolder(org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest) Tests in error: org.jboss.tools.jsf.ca.test.WebContentAssistProviderTest(org.jboss.tools.test.util.ProjectImportTestSetup) Tests run: 37, Failures: 4, Errors: 1, Skipped: 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7157) org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest fails

by Alexey Kazakov (JIRA)

org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest fails -------------------------------------------------------------- Key: JBIDE-7157 URL: https://jira.jboss.org/browse/JBIDE-7157 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.0.Beta2 junit.framework.AssertionFailedError: Root change is null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.tests.AbstractRefactorTest.checkChanges(AbstractRefactorTest.java:96) at org.jboss.tools.tests.AbstractRefactorTest.checkMove(AbstractRefactorTest.java:59) at org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest.testMoveCompositeComponentFile(JSF2RefactoringTest.java:81) junit.framework.AssertionFailedError: Root change is null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.tests.AbstractRefactorTest.checkChanges(AbstractRefactorTest.java:96) at org.jboss.tools.tests.AbstractRefactorTest.checkMove(AbstractRefactorTest.java:59) at org.jboss.tools.jsf.test.refactoring.JSF2RefactoringTest.testMoveCompositeComponentFolder(JSF2RefactoringTest.java:99) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7155) testMessagePropertyRename(org.jboss.tools.jsf.test.refactoring.MessagePropertyRefactoringTest) fails

by Alexey Kazakov (JIRA)

testMessagePropertyRename(org.jboss.tools.jsf.test.refactoring.MessagePropertyRefactoringTest) fails ---------------------------------------------------------------------------------------------------- Key: JBIDE-7155 URL: https://jira.jboss.org/browse/JBIDE-7155 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.0.Beta2 junit.framework.AssertionFailedError: There is unexpected number of changes expected:<2> but was:<1> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at org.jboss.tools.tests.AbstractRefactorTest.checkChanges(AbstractRefactorTest.java:97) at org.jboss.tools.tests.AbstractRefactorTest.checkRename(AbstractRefactorTest.java:43) at org.jboss.tools.jsf.test.refactoring.MessagePropertyRefactoringTest.testMessagePropertyRename(MessagePropertyRefactoringTest.java:59) 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:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7154) testELVariableRename(org.jboss.tools.jsf.test.refactoring.ELVariableRefactoringTest) fails

by Alexey Kazakov (JIRA)

testELVariableRename(org.jboss.tools.jsf.test.refactoring.ELVariableRefactoringTest) fails ------------------------------------------------------------------------------------------ Key: JBIDE-7154 URL: https://jira.jboss.org/browse/JBIDE-7154 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.0.Beta2 junit.framework.AssertionFailedError: There is unexpected number of changes expected:<3> but was:<1> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at org.jboss.tools.tests.AbstractRefactorTest.checkChanges(AbstractRefactorTest.java:97) at org.jboss.tools.tests.AbstractRefactorTest.checkRename(AbstractRefactorTest.java:43) at org.jboss.tools.jsf.test.refactoring.ELVariableRefactoringTest.testELVariableRename(ELVariableRefactoringTest.java:50) 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:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7162) org.jboss.tools.jsf.text.ext.hyperlink.JsfJSPTagNameHyperlink fails

by Alexey Kazakov (JIRA)

org.jboss.tools.jsf.text.ext.hyperlink.JsfJSPTagNameHyperlink fails ------------------------------------------------------------------- Key: JBIDE-7162 URL: https://jira.jboss.org/browse/JBIDE-7162 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.0.Beta2 testStyleClassOpenOns(org.jboss.tools.jsf.text.ext.test.OpenOnsTest) Time elapsed: 1.012 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.jsf.text.ext.test.OpenOnsTest.testStyleClassOpenOns(OpenOnsTest.java:234) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7167) EL validation doesn't work in JSPs.

by Alexey Kazakov (JIRA)

EL validation doesn't work in JSPs. ----------------------------------- Key: JBIDE-7167 URL: https://jira.jboss.org/browse/JBIDE-7167 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 The patch for JBIDE-7021 broke EL validation for JSPs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7213) OpenOn and Content Assist doesn't work properly for jsp page

by Vlado Pakan (JIRA)

OpenOn and Content Assist doesn't work properly for jsp page ------------------------------------------------------------ Key: JBIDE-7213 URL: https://jira.jboss.org/browse/JBIDE-7213 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta1 Environment: JBT 3.2.0.v20100925-0935-H92-Beta1 Linux 32bit Java Sun JDK 1,6 Reporter: Vlado Pakan Assignee: Alexey Kazakov Priority: Critical 1. Create New JSF Kick Start project 2. Open inputUserName.jsp page Open on doesn't work on neither on '#{Message.prompt_message}' or '#{user.name}' selection. Code assist for #{|} offered only 'user' EL but should offer also 'Message' EL. For xhtml page created within the same JSF project everything 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
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 November 2010