Hi,
if I understand, you have an application working fine without OJB and you want to use
OJB to import data from different database structure.
I think it's a good idea :
simply extend your class and define one class per import "way".
base class : A.class
define AfromDS1.class extends A
define AfromDS2.class extends A
...
declare your mapping on the repository (with specific data source and mapping).
So, simply "materialize" object with persistenceBroker :
PB.getCollection(AfromDS1.class) (with or without criteria)
You can now save each object (casted on A instance) with your application persistence
mechanism.
No impact on your application.
No code (simply declare extended classes and param. repository).
nice way, isn't it ?
----- Original Message -----
From: Christian Plate
To: '[EMAIL PROTECTED]'
Sent: Thursday, October 16, 2003 10:06 AM
Subject: Is OJB the right solution?
Hi!
After much reading i'm still not quite sure if OJB is the right
solution for our problem.
We have an existing Objectmodel and underlying Database. Now we
want to import data from other Datasources. These Datasources have
different Structures. So we thought it would be a good idea to find a
generic solution. The specification of a mapping through XML is
excactly what we need.
My Question is if OJB is the right solution for this
'Import-Scenario'. Should i look for something different?
Thanks in advance!
Christian Plate
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003
