November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5111) Fix failed junit tests after changing selection mechanizm

by Maxim Areshkau (JIRA)

Fix failed junit tests after changing selection mechanizm --------------------------------------------------------- Key: JBIDE-5111 URL: https://jira.jboss.org/jira/browse/JBIDE-5111 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Yura Zhishko Fix For: 3.1.0.CR1 For driving selection border for element we have used inFlasher xpcom interface. Now we draw this border modifying style attribute, adding such lines to style "border: 2px solid blue;". See function XulRunnerEditor.drawElementOutline(...).https://jira.jboss.org/jira/brows... Some of test begin failed with following exception, fix them. junit.framework.AssertionFailedError: string is"border: 2px solid blue; width: 1000px; background-color: white;" but must be "width: 1000px; background-color: white;" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareElements(ComponentContentTest.java:136) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:95) at org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest.testPageWithWidthsPixels(RichFacesComponentContentTest.java:356) 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 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 junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) 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: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:114) 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:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) 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:194) 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:368) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4373) Recreate OpenOn mechanizm for Visual Part of VPE

by Maxim Areshkau (JIRA)

Recreate OpenOn mechanizm for Visual Part of VPE ------------------------------------------------ Key: JBIDE-4373 URL: https://jira.jboss.org/jira/browse/JBIDE-4373 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.M1 We can call open on action from visual part and from source part. Now we have two difference implementations of openOn from source and visual part. We should use one source implementation. -- 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

16 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4812) JSF 2: CSS as a resource

by Juergen Zimmermann (JIRA)

JSF 2: CSS as a resource ------------------------ Key: JBIDE-4812 URL: https://jira.jboss.org/jira/browse/JBIDE-4812 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Environment: Eclipse 3.5.0, WTP 3.1, JBossTools nightly 200908211801-H205 Reporter: Juergen Zimmermann Fix For: 3.1.0.M3 CSS is not considered when using JSF 2. A CSS file can be referenced as a resource: <link rel="stylesheet" type="text/css" href="#{resource['css:hska.css']}"/> This is just the same resource referencing as for images. See https://jira.jboss.org/jira/browse/JBIDE-2550 -- 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

16 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4509) OpenOn from taglib definition file

by Maxim Areshkau (JIRA)

OpenOn from taglib definition file ---------------------------------- Key: JBIDE-4509 URL: https://jira.jboss.org/jira/browse/JBIDE-4509 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Maxim Areshkau Assignee: Maxim Areshkau -- 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

16 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5201) Smooks editor - update language of strings

by Brian Fitzpatrick (JIRA)

Smooks editor - update language of strings ------------------------------------------ Key: JBIDE-5201 URL: https://jira.jboss.org/jira/browse/JBIDE-5201 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Critical Go through all visible strings in the Smooks editor and update the text to be more English-readable. This will include not only labels and buttons, but also any dialogs, error messages, warnings, and so on. This could occur before externalization (JBIDE-5155) but MUST occur by end of November. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-949) Inconsistent menu titles of add/remove jsf capabilities

by Jiri Peterka (JIRA)

Inconsistent menu titles of add/remove jsf capabilities ------------------------------------------------------- Key: JBDS-949 URL: https://jira.jboss.org/jira/browse/JBDS-949 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: jbdevstudio-eap-linux-gtk-3.0.0.v200911160033M-H92-M4.jar Linux 32 bit Reporter: Jiri Peterka Priority: Minor Fix For: LATER Different menu titles for same operation: In Web Project: Remove Red Hat capabilities Package Explorer: JBoss Tools -> Remove JSF Capabilities It should be unified -- 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

16 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5283) NPE while deleting JSF project.

by Aliaksey Nis (JIRA)

NPE while deleting JSF project. ------------------------------- Key: JBIDE-5283 URL: https://jira.jboss.org/jira/browse/JBIDE-5283 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis EXECUTE: Create any JSF Kickstart project. EXECUTE: In Package Explorer or in Web Projects view select this project. EXECUTE: Press Delete button. FAILURE: Exception thrown in Error log. Error log 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

16 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-828) A JBDS generated WAR project with reverse-engineered entities doesn't work

by Ondrej Skutka (JIRA)

A JBDS generated WAR project with reverse-engineered entities doesn't work -------------------------------------------------------------------------- Key: JBDS-828 URL: https://jira.jboss.org/jira/browse/JBDS-828 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Ondrej Skutka Priority: Critical Fix For: 2.1.0 A patch proposed in JBSEAM-4276 is not applied into JBDS seam war project creation. -- 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

16 years, 4 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5232) Refactoring methods and properties of managed bean doesn't work for corresponding ELs.

by Alexey Kazakov (JIRA)

Refactoring methods and properties of managed bean doesn't work for corresponding ELs. -------------------------------------------------------------------------------------- Key: JBIDE-5232 URL: https://jira.jboss.org/jira/browse/JBIDE-5232 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR1 1. Create JSF 1.2. KickStart 2. Open User.java 3. Rename getName() to getFirstName() (use java refactoring) 4. Open hello.jsp 5. #{user.name} should be #{user.firstName}. But now there is unchanged #{user.name}. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-535) workflow/usability questions - Step 4: Select Java VM

by Nick Boldt (JIRA)

workflow/usability questions - Step 4: Select Java VM ----------------------------------------------------- Key: JBDS-535 URL: https://jira.jboss.org/jira/browse/JBDS-535 Project: Developer Studio Issue Type: Quality Risk Components: installer Affects Versions: 2.0.0.cr1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Attachments: Screenshot- JBoss Developer Studio 2.0.0.CR1.png Actually, it says "gij" but on my monitor the text is cut off and it looks like a q, not a g. Perhaps we could rework this as follows: "JBoss Developer Studio requires a Java 5 or later runtime. Gnu Java (gij) is not supported; Open JDK 6 is recommended. Choose the Java VM to use with JBoss Developer Studio. ( ) Default Java VM (defined by PATH) ( ) Alternate Java VM (user-defined)" Of course that assumes that JDBS *does in fact support JDK6*, and that we'd like to encourage people to use the latest and greatest Open JDK [1] (offered OOTB in Fedora 9 and later [2]), rather than letting them pick Sun, IBM, or BEA's JDKs. [1] http://openjdk.java.net/ [2] http://fedoraproject.org/wiki/JavaFAQ Also, does the installer check if the version of java used to run it is a compatible one? For example, will the installer run with 1.4, or with blackdown or gij, but require that JBDS itself use 5.0+? And, since this selection is a prereq before JBDS will work at all, should this page be step 1, not 4? -- 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

16 years, 4 months

2
11
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 2009