Menu
▾
▴
hibernate-issues
|
From: <no...@at...> - 2005-04-30 03:21:00
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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: Fri, 29 Apr 2005 10:20 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 |
|
From: <no...@at...> - 2005-04-30 10:33:08
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Sat, 30 Apr 2005 5:32 AM
Body:
I have no idea of what you are talking about - seriously!
Is there a bug you want to report or ?
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_17502
---------------------------------------------------------------------
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: Sat, 30 Apr 2005 5:32 AM
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
|
|
From: <no...@at...> - 2005-04-30 15:23:01
|
The following comment has been added to this issue:
Author: Jesse Kuhnert
Created: Sat, 30 Apr 2005 10:22 AM
Body:
Ummm actually, no. There appears to be a changed version in cvs already as we speak, so I guess it's just being developed way too much for bug postings yet. Sorry for the jumping the gun.
j
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_17503
---------------------------------------------------------------------
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: Sat, 30 Apr 2005 10:22 AM
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
|
|
From: <no...@at...> - 2005-05-02 00:23:39
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sun, 1 May 2005 7:22 PM
Body:
I think he's referring to thi:
http://forum.hibernate.org/viewtopic.php?p=2240353#2240353
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_17515
---------------------------------------------------------------------
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:22 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
|
|
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
|
|
From: <no...@at...> - 2005-05-03 16:03:37
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 3 May 2005 11:02 AM
Body:
Basically, the current situation is that we do not support polymorphism in the XML. I think this will not get fixed in May, and we should think about looking at it again in June.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_17551
---------------------------------------------------------------------
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: Tue, 3 May 2005 11:02 AM
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
|
|
From: <no...@at...> - 2005-05-03 16:03:38
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@hi...) --------------------------------------------------------------------- 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: Open Priority: Minor Original Estimate: 1 week Time Spent: Unknown Remaining: 1 week Project: Hibernate3 Components: core Versions: 3.0.2 Assignee: Gavin King Reporter: Jesse Kuhnert Created: Fri, 29 Apr 2005 10:20 PM Updated: Tue, 3 May 2005 11:02 AM 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 |
|
From: <no...@at...> - 2005-05-10 17:13:34
|
The following issue has been updated:
Updater: Preston Sheldon (mailto:pk...@ho...)
Date: Tue, 10 May 2005 12:13 PM
Comment:
Here is a TestCase which illustrates this issue.
Changes:
Attachment changed to XMLSubclassTest.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=history
---------------------------------------------------------------------
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: Open
Priority: Minor
Original Estimate: 1 week
Time Spent: Unknown
Remaining: 1 week
Project: Hibernate3
Components:
core
Versions:
3.0.2
Assignee: Gavin King
Reporter: Jesse Kuhnert
Created: Fri, 29 Apr 2005 10:20 PM
Updated: Tue, 10 May 2005 12:13 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
|
|
From: <no...@at...> - 2005-07-08 17:24:20
|
The following issue has been updated:
Updater: Steve Ebersole (mailto:st...@hi...)
Date: Fri, 8 Jul 2005 12:23 PM
Changes:
priority changed from Minor to Major
Fix Version changed to 3.1 beta
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=history
---------------------------------------------------------------------
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: Open
Priority: Major
Original Estimate: 1 week
Time Spent: Unknown
Remaining: 1 week
Project: Hibernate3
Components:
core
Fix Fors:
3.1 beta
Versions:
3.0.2
Assignee: Gavin King
Reporter: Jesse Kuhnert
Created: Fri, 29 Apr 2005 10:20 PM
Updated: Fri, 8 Jul 2005 12:23 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
|
|
From: <no...@at...> - 2005-07-08 17:33:25
|
Message: The following issue has been re-assigned. Assignee: Steve Ebersole (mailto:st...@hi...) --------------------------------------------------------------------- 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: Open Priority: Major Original Estimate: 1 week Time Spent: Unknown Remaining: 1 week Project: Hibernate3 Components: core Fix Fors: 3.1 beta Versions: 3.0.2 Assignee: Steve Ebersole Reporter: Jesse Kuhnert Created: Fri, 29 Apr 2005 10:20 PM Updated: Fri, 8 Jul 2005 12:33 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 |
|
From: <no...@at...> - 2005-07-08 20:59:18
|
The following issue has been updated:
Updater: Steve Ebersole (mailto:st...@hi...)
Date: Fri, 8 Jul 2005 3:57 PM
Comment:
This should be after 3.1
Changes:
Fix Version changed from 3.1 beta
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=history
---------------------------------------------------------------------
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: Open
Priority: Major
Original Estimate: 1 week
Time Spent: Unknown
Remaining: 1 week
Project: Hibernate3
Components:
core
Versions:
3.0.2
Assignee: Steve Ebersole
Reporter: Jesse Kuhnert
Created: Fri, 29 Apr 2005 10:20 PM
Updated: Fri, 8 Jul 2005 3:57 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
|
|
From: <no...@at...> - 2005-07-12 06:51:12
|
The following comment has been added to this issue:
Author: Stefan Wachter
Created: Tue, 12 Jul 2005 1:50 AM
Body:
Will the fix be ported to the 3.0.x versions?
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_18763
---------------------------------------------------------------------
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: Open
Priority: Major
Original Estimate: 1 week
Time Spent: Unknown
Remaining: 1 week
Project: Hibernate3
Components:
core
Versions:
3.0.2
Assignee: Steve Ebersole
Reporter: Jesse Kuhnert
Created: Fri, 29 Apr 2005 10:20 PM
Updated: Tue, 12 Jul 2005 1:50 AM
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
|
|
From: Steve E. (JIRA) <no...@at...> - 2005-10-14 21:02:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- 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...) was: 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...) Fix Version: 3.2 > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-02-16 19:32:21
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: (was: 3.2) 3.2 tmp > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2 tmp > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Oliver Li (JIRA) <no...@at...> - 2006-03-13 09:16:34
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=comments#action_22460 ] Oliver Li commented on HHH-422: ------------------------------- I encountered very simlar issue in my project. And we are using hibernate 3.0.5. So is the HHH 606, wrong-class exception on joined-subclass has been fixed, I saw that issue has been closed. Thanks. > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.0 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-16 15:38:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: (was: 3.2.0.alpha2) 3.2.0 > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.0 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-27 17:36:29
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0 cr1) > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.0 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:28
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.0 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:46:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: 3.2.2 (was: 3.2.0.cr3) > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.2 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > 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...) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X