non-SQL persistant tree-like CRUD

[timotheus2]

I am creating a CRUD application as follows.

(1) Module "ModuleData" has a serializable tree of POJOs (set and get data objects). Level0 contains a list of Level1 objects. Level1 has data fields and a list of Level2 objects. Level2 has different data fields and list of Level3 objects. Level3 has data fields that differ from the other levels.

(2) Module "ModuleExplorer" has an explorer window that uses the Nodes API to show a root folder as Level0; which expands to a list of Level1 nodes, which then expand to show lists of Level2 nodes downto Level3, similar to the FeedReader tutorial.

(3) Module "ModuleEditor" has an editor window with text fields to edit the POJO fields, similar to the CRUD tutorial. A panel class exists that correlates to each of the POJOs.


I am somewhat confused. How do I start implementing the following using the Netbeans APIs?

(a) Whenever a node is selected in the explorer window, a different panel with different fields should be active in the editor window.

(b) Only one tree of instances of the Level0-2 objects should be created. Those instances need to be associated with both the nodes in the explorer window and the editor window. For every node the corresponding data/level object should exist. And for ever data/level object, the corresponding editor panel should exist and be displayed.


Is this a good low-coupling implementation, or should I be attempting the same functionality in a different way?

[tomwheeler]

It's rather late on a Friday, so I will preface my advice by saying I
probably didn't understand every detail of your explanation. But the
two pieces of advice I'd offer are:

You can (and almost certainly should) use Lookups for loosely-coupled
communication between things in NetBeans. This is probably the most
important oy any NetBeans API, so I recommend reading up on it:

http://wiki.netbeans.org/DevFaqLookup

It sounds to me like you're trying to create a master-detail view or
some variation thereof. If so, the orange "Rich Client Programming"
book by Tim Boudreau, Jaroslav Tulach and Geertjan Wielenga has an
example (and lots of explanation) for something similar in chapter 9.

On Fri, Oct 2, 2009 at 5:49 PM, timotheus2 <address-removed> wrote: