Menu
▾
▴
hibernate-issues
|
From: <no...@at...> - 2005-05-04 05:17:37
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 Here is an overview of the issue: --------------------------------------------------------------------- Key: HHH-434 Summary: element/@attribute not implement for collection elements Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Hibernate3 Components: core Versions: 3.0.3 Assignee: Reporter: Gavin King Created: Wed, 4 May 2005 12:17 AM Updated: Wed, 4 May 2005 12:17 AM Description: None of the following: <element> <one-to-many> <many-to-many> support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. We need to find some design where this can be made more flexible. Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. Any volunteers? --------------------------------------------------------------------- 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-04 05:19:38
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@hi...)
Date: Wed, 4 May 2005 12:19 AM
Changes:
summary changed from element/@attribute not implement for collection elements to element/@attribute not implemented for collection elements
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-434
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HHH-434
Summary: element/@attribute not implemented for collection elements
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate3
Components:
core
Versions:
3.0.3
Assignee:
Reporter: Gavin King
Created: Wed, 4 May 2005 12:17 AM
Updated: Wed, 4 May 2005 12:19 AM
Description:
None of the following:
<element>
<one-to-many>
<many-to-many>
support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case).
This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods.
We need to find some design where this can be made more flexible.
Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution.
Any volunteers?
---------------------------------------------------------------------
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-06-19 00:04:02
|
The following comment has been added to this issue:
Author: David Betts
Created: Sat, 18 Jun 2005 7:03 PM
Body:
I'm willing to help out here; unfortunately I don't follow the proposed solutions. I think I lack a good understanding of how all these pieces hang together. If its worth the effort, could some elaborate a little?
Thanks,
--david
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=comments#action_18345
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-434
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HHH-434
Summary: element/@attribute not implemented for collection elements
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate3
Components:
core
Versions:
3.0.3
Assignee:
Reporter: Gavin King
Created: Wed, 4 May 2005 12:17 AM
Updated: Sat, 18 Jun 2005 7:03 PM
Description:
None of the following:
<element>
<one-to-many>
<many-to-many>
support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case).
This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods.
We need to find some design where this can be made more flexible.
Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution.
Any volunteers?
---------------------------------------------------------------------
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-11-10 14:55:43
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Environment: Description: None of the following: <element> <one-to-many> <many-to-many> support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. We need to find some design where this can be made more flexible. Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. Any volunteers? was: None of the following: <element> <one-to-many> <many-to-many> support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. We need to find some design where this can be made more flexible. Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. Any volunteers? Fix Version: 3.2 > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: (was: 3.2) 3.2 tmp > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2 tmp > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: (was: 3.2.0.alpha2) 3.2.0 > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2.0 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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:39
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: (was: 3.2.0 cr1) 3.2.0 > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2.0 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2.0 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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:24
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: 3.2.2 (was: 3.2.0.cr3) > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2.2 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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