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.

Bug 19316 - Allow customization of the DataObject editor's corresponding in place editor
Summary: Allow customization of the DataObject editor's corresponding in place editor
Alias: None
Product: platform
Classification: Unclassified
Component: Property Editors (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ tboudreau
Depends on: 29447
Blocks: 19851
  Show dependency tree
Reported: 2002-01-11 05:18 UTC by Rochelle Raccah
Modified: 2008-12-22 19:34 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Rochelle Raccah 2002-01-11 05:18:32 UTC
There is special code I'd like to put in setAsText, getAsText, and getTags. 
Please see the thread on nbdev:
Comment 1 Marek Grummich 2002-07-22 08:34:59 UTC
Target milestone was changed from '3.4' to TBD.
Comment 2 Marek Grummich 2002-07-22 08:49:57 UTC
Target milestone was changed from '3.4' to TBD.
Comment 3 Marian Mirilovic 2002-12-06 17:09:37 UTC
reassigne to Tim, new owner of property editors.
Comment 4 _ tboudreau 2003-07-18 19:00:50 UTC
There is a very clean, easy solution that requires no changes in
the core DataObject editor.  And since it appears to be 
decided that DataSystems in its current form is going away,
this solution has the advantage of being able to work 
transparently with any replacement for DataObjectEditor:

Write a wrapper property editor, along the lines of

class MyDataObjectEditor implements PropertyEditor {
  private PropertyEditor wrapped;
  public MyDataObjectEditor (PropertyEditor toWrap) {
    wrapped = toWrap;
  public void setAsText(String s) {
    //do your validation (remember to annotate exceptions correctly!)
    wrapped.setAsText (s);

Then, in your DataNode subclass:
  public PropertyEditor getPropertyEditor() {
     return new MyDataObjectEditor (super.getPropertyEditor());
Comment 5 Rochelle Raccah 2003-07-19 01:14:07 UTC
Doesn't your solution assume I own the DataNode?  What if I pick
another module's data object?
Comment 6 _ tboudreau 2003-07-19 02:54:52 UTC
If you're providing hints to its property editor, well, I 
would hope you own it...tell me you're not calling
setValue() on JavaDataObjects to alter the behavior of 
their property editors!  

Comment 7 Rochelle Raccah 2003-07-22 00:54:09 UTC
No - I'm providing a property editor on my own node which allows the
user to pick a different JavaDataObject.  For example, imagine an
implements property which allows you to point to a JavaDataObject.
Comment 8 Marian Mirilovic 2003-07-25 18:34:01 UTC
Comment 9 _ tboudreau 2003-07-28 12:50:05 UTC
Okay.  For that case, you should still provide a wrapper
property which can expose the original java node property,
but provide its own hints.  The fact
that a module can, in theory, play with the hints available
from a foreign node is, IMO, a fairly awful design flaw that
certainly should not be exploited.