>If I have a business object, is it better for the bizobj to directly access the data, or should I have separate set of 'data objects' that the bizobj communicates with?
>
>Most examples I have seen are simplified for ease of communicating the ideas and seem to gloss over how this should be handled.
>
>Ideas, thoughts?

I do like a consistent architecture and try to pay attention to structural issues. To me, a level of abstraction is important as a bridge between 2 distinctly different ways of looking at the world. Distinctly different terms and languages are appropriate in either of the two worlds bridged by that layer.

From using bizobjs, it seems that they mediate between high level end user business rules on the one hand, and low level data manipulation on the other. The data manipulation part is, if I understand, simply the work of what your set of data objects would be.

Certainly, there are different levels of abstraction working with data -- but it's all the same language. Here, using methods called by other methods might well achieve the abstraction you're looking for -- in the spirit of structured programming.

I guess the one thing that comes across is that there are no "easy" answers in OO. But, somehow, like riding a bike, we all get better with practice %).

That's my take. I'm sure others have their distinct point of view.

Jay