[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-1073) Patch to make working ReverseEngineeringStrategy.isForeignKeyCollectionLazy

Max Rydahl Andersen (JIRA) noreply at atlassian.com
Mon Jul 14 17:48:42 EDT 2008


    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30658 ] 

Max Rydahl Andersen commented on HBX-1073:
------------------------------------------

hmm....surprised my test for this doesn't fail...any case you created a testcase too ?

In any way thanks for the patch - I'll look into to getting it in asap.

> Patch to make working ReverseEngineeringStrategy.isForeignKeyCollectionLazy
> ---------------------------------------------------------------------------
>
>                 Key: HBX-1073
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1073
>             Project: Hibernate Tools
>          Issue Type: Patch
>          Components: reverse-engineer
>    Affects Versions: 3.2.1, 3.2.2, 3.2LATER
>         Environment: HibernateTools-3.2.2.Beta1, Mysql-5.0
>            Reporter: Oleg Panashchenko
>         Attachments: patch-reveng-isForeignKeyCollectionLazy.diff
>
>
> Function ReverseEngineeringStrategy.isForeignKeyCollectionLazy from custom reverse engineering strategy, according to JavaDoc, should control whether generated collection is lazy or not. However, boolean value, which the function returns, is ignored by reverse engineering tool, and collection is always generated lazy, which is default.
> Changes.
> - If the function isForeignKeyCollectionLazy returns false, the patch adds lazy="false" to appropriate collection entry into proper .hbm.xml file.
> - The patch adds another function, ReverseEngineeringStrategy.isForeignKeyReferenceLazy with the same signature as the original one. The new function controls laziness of the reverse side of the collection.
> The patch does not change default behavior of the reverse engineering tool, when the above strategy functions are not present in a custom strategy Java file.

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

        



More information about the hibernate-issues mailing list