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 |