| Summary: | converter property cannot be set for MultiBinding due to Introspector odd behavior | ||
|---|---|---|---|
| Product: | [Technology] XWT | Reporter: | Mario Curcija <mario.curcija> |
| Component: | Core | Assignee: | Project Inbox <e4.xwt-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Attachments: | |||
|
Description
Mario Curcija
Created attachment 171334 [details]
MultiBinding Tests patch showing "converter" not settable
Created attachment 180558 [details]
Simplest check for Multibinding's converter property
Sun's Inrospector implementation in 1.6.0_21 is never unable to find setter for converter property. On the other hand gjc's (1.5.0) Introspector implementation does succeed (although not always :)
(In reply to comment #2) > Sun's Inrospector implementation in 1.6.0_21 is never unable to find setter for "always unable to find setter for" Created attachment 180559 [details] Sun's Bug 6852569 adoped for MultiBinding's class hierarchy Reference to Sun's JDK Bug: Introspector.getBeanInfo ignores write method if read method is overridden http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=e4671321ad8dd14a8ba92e190ca2e?bug_id=6852569 |