Hi all, Here's is a comment from a first time OJB user. I had to do a web project with a quiet large entity relationship model. Many 1toN and MtoN relations. So what do you do?!
- You make up your model. I use UML. - Look for a case tool where you can generate some code. Poseidon is great. - Put in the your xdoclet tags for the mapping. - Put in your xdoclet tags for the form beans. - May be write a couple conversion classes from form beans to businessobjects and from businessobjects to DB. - Write an Interface for Querying your objects the way you need them. That's it. Straight forward! 28 tables and not a single line of SQL. But it is not about SQL. I love this approach so much, because you just maintain one set of classes and manage everything through the xdoclet attributes. When I think of the system now I stay fully in my model. No more and then I have to insert that FK there... In fact if we had more stable computer I would write the PersistenceBrokerEmpty implementation ;-) Maybe it isn't the most efficient way to materialize an object with its relations or just a complete row if you only need a single entry. But why not next time it's gonna be in cache, who the hell cares in times of cheap memory. This is next millennium?! If you think in an OO way and if need a relational DB in the back you don't get around O/R mapping. GreetZ Nils --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
