October 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-819) Driver properties for DefaultDS connection profile cannot be changed in Connection Profile properties dialog

by Denis Golovin (JIRA)

Driver properties for DefaultDS connection profile cannot be changed in Connection Profile properties dialog ------------------------------------------------------------------------------------------------------------ Key: JBDS-819 URL: https://jira.jboss.org/jira/browse/JBDS-819 Project: Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Denis Golovin Fix For: 2.1.0, 3.0.0.M3 -- 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
5
0 / 0

[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: (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: (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

[JBoss JIRA] Created: (JBDS-854) Testing examples with TestNG plugin fails

by Martin Gencur (JIRA)

Testing examples with TestNG plugin fails ----------------------------------------- Key: JBDS-854 URL: https://jira.jboss.org/jira/browse/JBDS-854 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Martin Gencur The bug is present in N200908281758-H140 build (the same result on windows and linux) When testing examples from seam with TestNG plugin in JBDS the test always throws java.lang.AssertionError. For example: in the booking example when running BookingTest.java with TestNG plugin, the test ends up with: FAILED: testBookHotel java.lang.AssertionError: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'hotelSearch' resolved to null at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:455) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:504) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.booking.test.BookingTest.testBookHotel(BookingTest.java:66) Caused by: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'hotelSearch' resolved to null at org.jboss.el.parser.AstValue.getTarget(AstValue.java:38) at org.jboss.el.parser.AstValue.setValue(AstValue.java:83) at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) at org.jboss.seam.mock.AbstractSeamTest$Request.setValue(AbstractSeamTest.java:430) at org.jboss.seam.example.booking.test.BookingTest$2.updateModelValues(BookingTest.java:47) at org.jboss.seam.mock.AbstractSeamTest$Request.updateModelValuesPhase(AbstractSeamTest.java:670) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:592) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) ... 37 more ... Removed 22 stack frames Another example: seam todo example ends up with: FAILED: testTodo java.lang.AssertionError: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'login' resolved to null at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:455) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:504) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.todo.test.TodoTest.testTodo(TodoTest.java:42) Caused by: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'login' resolved to null at org.jboss.el.parser.AstValue.getTarget(AstValue.java:38) at org.jboss.el.parser.AstValue.setValue(AstValue.java:83) at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) at org.jboss.seam.mock.AbstractSeamTest$Request.setValue(AbstractSeamTest.java:430) at org.jboss.seam.example.todo.test.TodoTest$1.updateModelValues(TodoTest.java:26) at org.jboss.seam.mock.AbstractSeamTest$Request.updateModelValuesPhase(AbstractSeamTest.java:670) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:592) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) ... 37 more ... Removed 22 stack frames Last example: seambay example ends up with: FAILED: testCreateAuction java.lang.AssertionError at org.jboss.seam.example.seambay.test.AuctionTest$1.invokeApplication(AuctionTest.java:26) at org.jboss.seam.mock.AbstractSeamTest$Request.invokeApplicationPhase(AbstractSeamTest.java:646) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:595) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.seambay.test.AuctionTest.testCreateAuction(AuctionTest.java:28) ... Removed 22 stack frames -- 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

[JBoss JIRA] Created: (JBIDE-3891) Add JUnit tests for org.jboss.tools.common.verification.ui.vrules.preferences

by Denis Golovin (JIRA)

Add JUnit tests for org.jboss.tools.common.verification.ui.vrules.preferences ----------------------------------------------------------------------------- Key: JBIDE-3891 URL: https://jira.jboss.org/jira/browse/JBIDE-3891 Project: Tools (JBoss Tools) Issue Type: Task Components: common Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 1. Create est plug-ins for common.verification 2. Create test suites 3. Include test suites into test builder build.properties -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4652) JBoss Tools Preferences doesn't support filtration correctly

by Yura Zhishko (JIRA)

JBoss Tools Preferences doesn't support filtration correctly ------------------------------------------------------------ Key: JBIDE-4652 URL: https://jira.jboss.org/jira/browse/JBIDE-4652 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.1.0.M2 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor 1) Open JBDS 2) Menu Window -> Preferences 3) In text field for filters enter "template" RESULT: JBoss Tools -> Web isn't expanded correctly (see screenshot-2) -- 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
10
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 October 2009