-----Original Message----- From: Mahler Thomas [mailto:[EMAIL PROTECTED] Sent: dinsdag 17 juni 2003 15:22 To: 'OJB Users List' Subject: RE: Questions re. mapping of associations...
[...] The most elegant way would be to have a simple factory method that is used to create Jav.util.List instances. In ODMG mode id serves DListImpls, in JDO mode a Vector or so. This would minimize the impact on your business model! ... I was thinking along these lines myself. But I was afraid that I would also have to change my field-declarations to 'DList' instead of 'List'. Glad that I don't have to :-) Still have to find a way make the proper factory-object available in all places where it needs to be... Right now, my objects are practically unaware of there being any persistence-layer and they will have to somehow get a reference to the instance of the persistence-provider abstraction layer. There can be multiple instances of multiple implementations at the same time - 1 to serve XML, 1 to serve DB. Perhaps 2 to serve different databases, if I want to compare performance of different databases or O/R mapping solutions. When creating an instance of one of my objects I will need to somehow specify which of the PersistenceProvider instances to choose from for creating List / Map instances! Do I just want too much? ;-) --Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
