Yeah I don't think the leafImpl property is valid anymore after the merge from the spring cartridge, so that probably should be removed, so I think a JIRA issue should probably still be created.
Chad -----Original Message----- From: David R. Allen [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 9:02 AM To: Chad Brandon; [email protected] Subject: Re: [Andromda-user] Inconsistent Factory and Mapping Files After examining the template for the *Factory class, I realized this behavior was caused by the "leafImpl" namespace property being set to true. Once I set it to false, the mappings and *Factory classes are all consistent. I guess I can still file a bug, but I am not sure exactly what the problem is with all this logic--it depends on the overall design to some degree. Nevertheless, there is this one case where it is inconsistent. On Wednesday 02 March 2005 10:41 am, Chad Brandon wrote: > Sounds like a bug in the factory class...can you file a JIRA issue? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David R. > Allen > Sent: Wednesday, March 02, 2005 8:28 AM > To: [email protected] > Subject: [Andromda-user] Inconsistent Factory and Mapping Files > > I am using the inheritance strategy "subclass" to get a table-per-subclass > hierarchy with the Hibernate cartridge. The factory classes and mappings > for > Hibernate are fine with the derived classes, but there is a problem with > the > > base classes, either due to a bug or something I have done wrong with the > configuration. > > Let class A be the base <<Entity>> class in the model, with two derived > classes B and C. For both B and C, the corresponding <joined-subclass> > elements use the *Impl class, and the main class element maps the *Impl > class > for entity A. > > The problem is in the generated *Factory classes where for A, the > findByPrimaryKey() method uses the A.class in the load() method, not the > AImpl.class. The corresponding methods for B and C are fine, and both use > the *Impl.class. Naturally, A.class cannot be used with Hibernate since it > does not exist in any mapping file (AImpl is mapped as it should be). > > Is there something I should have done in the namespace properties or model? > > Thanks, -- David Allen [EMAIL PROTECTED] ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
