Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321539 - [DataBinding] testSetValueThrowsExceptionThrownByBea fails by threw exception:Method not found: isValue
Summary: [DataBinding] testSetValueThrowsExceptionThrownByBea fails by threw exception...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-02 18:25 EDT by Tao Zhang CLA
Modified: 2019-11-14 03:49 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tao Zhang CLA 2010-08-02 18:25:15 EDT
Build Identifier: 3.4.2

The test testGetValueThrowsExceptionThrownByBea in  org.eclipse.jface.tests.databinding_win32.win32.x86.html threw exceptions as below by running eclipse auto tests in jdk 7 b102:
need to know that because why isValue not found.
Method not found: isValue java.beans.IntrospectionException: Method not found: isValue
at java.beans.PropertyDescriptor.<init>(PropertyDescriptor.java:106)
at java.beans.PropertyDescriptor.<init>(PropertyDescriptor.java:70)
at org.eclipse.core.tests.internal.databinding.beans.JavaBeanObservableValueTest.testGetValueThrowsExceptionThrownByBean(JavaBeanObservableValueTest.java:84)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195)
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 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)
at org.eclipse.core.launcher.Main.main(Main.java:30)



Reproducible: Always

Steps to Reproduce:
1. Install jdk 7 b102 which can be downloaded from:
http://download.java.net/openjdk/jdk7/
2. Run the eclipse auto test (3.4.2)
3. You will see the failure
Comment 1 Remy Suen CLA 2010-08-02 18:38:19 EDT
Does it work with Java 6? Do the 3.6 tests pass?
Comment 2 Matthew Hall CLA 2010-08-20 02:03:16 EDT
Tao Zhang, is this the full stack trace?  There is nothing in the JavaBeanObservableValueTest.testGetValueThrowsExceptionThrownByBean method that directly references the PropertyDescriptor class, so I'm not sure how to approach this.

I want to make clear though that technically JDK7 isn't officially supported yet since it is still in beta, and no spec has even been finalized for Java7.  The fact that the test suite runs successfully every day during our build, yet fails under JDK7 seems to indicate that there is a regression in JDK7 itself.
Comment 3 Matthew Hall CLA 2011-09-14 01:21:41 EDT
Tao Zhang: please try this again with the Java 7 SE release and let me know whether this is still a problem.
Comment 4 Lars Vogel CLA 2019-11-14 03:49:29 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.