Thanks Jan, Jan Kodera wrote:
Hi, I think one way is this. As a connector for this classes use xwiki document. I mean you have two xwiki classes. One is FishProvider and other one is Fishes or for each fish species one class. You connect both of them by adding them to some xwiki document. So you will get unique connection for FishProvider and Fishes.
For example you have class Fish1 and class FishProvider. Fish1 will have propertie like size. FishProvider will have propertie like name.
Now you create xwiki document, for example with name Fishery, and as next step you create object for class Fish1 and another object for class FishProvider. These two objects is now attached to xwiki document Fishery. In database it connected throught table XWikiObjects.
I hope that, it will help you.
Jan
Yes, the document is a nice metaphor where we can instantiate both freshFishProviderClass and speciesClass. But consider this: species 1, 2 and 3 have all three the same properties (at least some properties) whatever provider supplies them. If I have to instantiate the speciesClass once for each provider providing each species, I am forced to repeat the same information for each object. The point is, when I have a speciesClass instance for a given species, let's say /Raja batis/, how could I "link" it to all and each providers providing it? This is clear to me in a relational schema, but not so clear in a object-oriented one; well, much better: not clear at all! :-) Thanks for your reply! Ricardo -- Ricardo RodrÃguez Your EPEC Network ICT Team