| Hi Michelle, Michael and I were talking this morning about a related issue with reading an object model and making some of the instances persistent. The test case we were talking about was the CompletenessTest but the results were relevant. What we decided as an approach is to define another object in the bean xml file called "root". This object is a List that contains all of the objects to become persistent. In the case of the CompletenessTest with no relationships, we need this to be able to instantiate instances of Company, Department, PartTimeEmployee, FullTimeEmployee, MedicalInsurance, DentalInsurance, and Project and individually persist them and compare them. We don't need to persist the Address because these are embedded. We discussed using this same approach for the QueryTest as well. Michael said he would look into modifying the query test to use the same pattern, and see if both tests could use the same company.xml input files. Considering persistence by reachability, the only objects needed in the "root" list is the root of the connected objects. I think in the case of the query test, it is the single object "dept1" that is in the "root" list. I suppose it can't hurt to have emp1, emp2, and emp3 in the root list as well, but it is only needed if the implementation has a bug in persistence by reachability. I don't think we need an "isEmbedded" feature in the CompanyModelReader. Craig On Jul 12, 2005, at 2:47 PM, Michelle Caisse wrote:
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! |
smime.p7s
Description: S/MIME cryptographic signature
