This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Original status: 7-Fix in Progress; Suggested Status: STARTED Original Target Release: shortfin_dev; Suggested Target Milestone : 5.5 Original submitter: mbohm Description: For instance, the itemNumber property of BuyNowPostData is a String, and uses com.sun.jsfcl.std.ValueBindingPropertyEditor. If you type a String directly into the property sheet, it does not take. And if you open the property editor dialog up, and type a String, it also does not take. BuyNowPostData.itemNumber is just an example. This is a general problem in the bp components. Note that this is not a regression; it was so in Leopard as well. Evaluation: Gregory recommends trying to replace com.sun.jsfcl.std.ValueBindingPropertyEditor with com.sun.rave.propertyeditors.binding.ValueBindingPropertyEditor (in the BeanInfos). If it works, the change should probably be made globally within the complib. Evaluation (Entry 2): Marking accepted. Evaluation (Entry 3): Marking fix in progress. I tried replacing most of the ValueBindingPropertyEditors as indicated by the attached diff, but, unfortunately, while this works well in shortfin, it gives leopard trouble, for instance, a ClassCastException thrown by ValueBindingPropertyEditor when interacting with the property sheet for a rating component. Evaluation (Entry 4): Lowering to P3/S3 (I was the submitter), since this is in the ajax complib, which is released post-FCS.
Accepting.
When I specify com.sun.jsfcl.std.ValueBindingPropertyEditor, I see the lame property editor; when I specify org.netbeans.modules.visualweb.propertyeditors.binding.ValueBindingPropertyEditor, I see the good property editor. I'm mystified, because in nb6, the latter extends the former with no changes. But I should not spend more time on this now, given the bug priorities. Changing from defect to enhancement.