[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3275) Allow pluggable tuplizers for composite elements

[Vincent Vandenschrick (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32315#action_32315 ] 

Vincent Vandenschrick commented on HHH-3275:
--------------------------------------------

Steve,
Modifying the DTD actually works. Here is what I did for testing purpose (Hibernate 3.2.5-GA) :
- extracted the "hibernate-mapping-3.0.dtd" from the Hibernate jar
- modified the "<!ELEMENT composite-element" section by adding "tuplizer*," just after "parent?,"
- created an "org.hibernate" package in my application codebase and copied the modified DTD (classpath precedence made this DTD resolved before the Hibernate default one).

Hibernate doesn't complain anymore and I successfully persisted and loaded the components collection with the custom component tuplizer.

Best regards,
Vincent


> Allow pluggable tuplizers for composite elements
> ------------------------------------------------
>
>                 Key: HHH-3275
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3275
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: metamodel
>            Reporter: Chris Bredesen
>            Assignee: Steve Ebersole
>            Priority: Minor
>
> By looking at the hibernate-mapping DTD, it does not seem possible to define a tuplizer for a composite-element.
> However, composite elements have component semantics, so if Hibernate allows pluggable tuplizer for components, one would expect the same thing about composite elements.

-- 
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