I will be using code generation to generate a data access layer. Each table
will have a class mapping on to the table and a class for generating
collections of the table class. These will then be used in business objects.
I would like to have things like e.g. a property which is a collection of
child objects. The obvious problem is you could potentially have collections
of objects containing collections of objects and so on. Are there any slick
design patterns which allow you to flexibly express how many level of
objects are loaded in? My objects will be served up through a web service
which makes the object calling methods on itself a little trickier (I am new
to web services) when it is on the client.
Regards, Chris.
|
Similar Threads
