[hibernate-issues] [Hibernate-JIRA] Updated: (ANN-716) Join table name cannot be resolved when using custom EJB3NamingStrategy

Emmanuel Bernard (JIRA) noreply at atlassian.com
Sat May 31 14:30:34 EDT 2008


     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated ANN-716:
---------------------------------

    Fix Version/s: 3.4.0.CR2

> Join table name cannot be resolved when using custom EJB3NamingStrategy
> -----------------------------------------------------------------------
>
>                 Key: ANN-716
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-716
>             Project: Hibernate Annotations
>          Issue Type: Bug
>          Components: binder
>    Affects Versions: 3.3.1.GA
>         Environment: Hibernate Core 3.2.6.GA
>            Reporter: Miroslav Havram
>             Fix For: 3.3.2, 3.4.0.CR2
>
>         Attachments: stack_trace.txt, test_case.zip
>
>
> When using custom implementation of the EJB3NamingStrategy, join table name for an optional One-To-Many relation cannot be resolved.
> Simple test case is attached.
> Related to:
> http://forum.hibernate.org/viewtopic.php?t=983065

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