Return to Answer

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good new is that as this creates a tree, you can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces doumented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

I would add hasChild() and nextChild() methods to implement iterations.

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good news is that as this creates a tree. You can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces documented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

I would add hasChild() and nextChild() methods to implement iterations.

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good new is that as this creates a tree, you can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces doumented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

UPDATE:

The UML diagram is taken from here.

I would add hasChild() and nextChild() methods to implement iterations.

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good new is that as this creates a tree, you can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces doumented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

I would add hasChild() and nextChild() methods to implement iterations.

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good new is that as this creates a tree, you can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces doumented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

One way to make it easier is that all classes implement the same interface so you can treat them indistinctly. Theres a known pattern for this:

The good new is that as this creates a tree, you can then write, in an external managing class, recursive methods to look up items.

For example you could write a method findAndAdd(String tagToFind, Component componentToAdd);

To the base interfaces doumented in the pattern you should add a tagMatches(String tag) as well as all common getters and setters so you can, again, treat items indistincltly of their class.

UPDATE:

The UML diagram is taken from here.

I would add hasChild() and nextChild() methods to implement iterations.