Hi Bruce If you stick to PM, then you can make it portable across containers. It's one step better than using a container's CMP2.0. In that situation, you are more locked in to the vendor. Not only do you need to write new descriptors, the results may differ if you decide to port.
Just going through CMP2.0's examples, I have managed to prototype a very complex data model with combinations of: 1-to-1 uni-directional 1-to-1 bi-directional 1-to-many uni-directional 1-to-many bi-directional many-to-many bi-directional It's awesome. PS: Note that I can achieve the same with Castor. Keith > -----Original Message----- > From: Bruce Snyder [mailto:[EMAIL PROTECTED]] > Sent: Saturday, 12 January 2002 9:02 a.m. > To: [EMAIL PROTECTED] > Subject: Re: [castor-dev] Castor for DAO's in an EJB app > > > Keith Chew wrote: > > > > Yes, and it comes with source. If you need help in setting > anything up, give > > me a buzz. Else, join the newsgroup for further discussion. > > > > Even if you are not going to use PM, just read the PDF > documentation. By the > > end of it, you'll be familiar with CMP2.0 and additonal > features required > > for a commercial standard application. > > > > Keith, > > You're right. The MVCSoft manual was extremely beneficial for me. Not > only is it very informative but it is also fairly well written. I > checked out the Persistence Manager during the Summer 2001 and I was > very impressed. Dan was very helpful to me with my questions. > > My only problem with CMP 2.0 is that it's not portable. > > Bruce > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
