From: <no...@at...> - 2005-05-02 00:39:35
|
The following comment has been added to this issue: Author: Jesse Kuhnert Created: Sun, 1 May 2005 7:38 PM Body: Yep, that's the daddy..The cvs browse I did earlier was accidently on the trunk, instead of the 3.0.2, so I thought things looked too different to be the same, but the existing problem/(my lack of understanding) is stil there. I just didn't want to post a bug for a feature that seems so new, and assumed that - based on the TODO comments inside the class - someone already had plans on fixing it and was probably off doing it somewhere in a dark corner, or alley, or wherever you do things like that. --------------------------------------------------------------------- View this comment: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_17517 --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 Here is an overview of the issue: --------------------------------------------------------------------- Key: HHH-422 Summary: xml entity bindings for subclass entities Type: Improvement Status: Unassigned Priority: Minor Original Estimate: 1 week Time Spent: Unknown Remaining: 1 week Project: Hibernate3 Components: core Versions: 3.0.2 Assignee: Reporter: Jesse Kuhnert Created: Fri, 29 Apr 2005 10:20 PM Updated: Sun, 1 May 2005 7:38 PM Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. Description: I'm sure someone else is already in the process of agnonizing over how to handle the entity name resolution issues that are currently floating around in the codebase, but for the sake of not knowing who's doing what and what-not (heh), I thought I would share my couple quick notes learned from trying to make this work today. I was having problems getting an import of xml data into hibernate with derived subclasses of one base class. (Not abstract, derived using the discriminator value column and table per subclass method). Was getting lots of errors trying to map my subclass nodes into the main xml document, even if I named the child nodes the same as the parent. The only eventual temporary solution I could find was by adding the subclass "node name" values into the two Map instances I could find that needed these references. [Mappings class and EntityPersister, ughh I've forgotten the other ones name now. ] The one main culprit already had an obvious method comment with a TODO tag so I'm sure someone is already working on a much better longterm solution than mine.. The only thing I didn't complete was having the ability for the subclass instances to have their own node names. Ie if I had an instance of the base class mapped as a many-to-XX collection in someone's class, I had to specify a node name of "something" to get it to be recognized. I didn't get far enough in my day to get this part as well, but I think it would just require being able to reference the current child somehow. Some sort of XSLT expression like "name()" or "self" perhaps? After that everything worked beautifully of course :) Will be very excited to see this feature come to full bloom, as I plan on using it to synchronize some data points with customer databases sometime this summer? (Am I being too hopeful? I'd love to help, but I'm sure there are plenty of good people doing things already..And I'm I'm fu#$!@ with my own deadlines anyways...) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |