I am working on a medium size project which use the composition pattern for
the structure of the data. The composition pattern basically means that
other objects are in a root object, recursively.

The problem we are now facing is that these objects become extremely large.
Following implemenations are in it:
- graphical representation (we are using swing)
- XML output generator
- physical formulas

All these parts are developed by different persons, but all make heavy use
of the tree structure.

One idea is to split it into different objects, having one object just
containing the tree.
class O {GRO g; XMLO x; PHYO p; List<O> others;}

Having the problem that g,x,p need also a list of others. So adding would be
not so nice.

Another idea is to have dozens of pass through functions like
class O {public void func (decl d1, decl d2,...)
       { // doing something with subobjects
       return g.func(d1,d2,...);} // doing implementation stuff
       private GRO g;
}
for functions making use of recursive calling and need subelements.

Any other ideas? How could that be solved elegant?

thank you for any ideas!
Markus