[hibernate-issues] [Hibernate-JIRA] Commented: (METAGEN-29) Embedded generic types not supported by metamodel generator

[Jeff Jensen (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37517#action_37517 ] 

Jeff Jensen commented on METAGEN-29:
------------------------------------

We have the same problem as this issue, and would like to try the snapshot you deployed, Hardy.

However, the snapshot deployed to [0] has problems ([1] and [2] {your URL}  have the same issue, but they may map to the same repo now?).  The deploy does not have the POM, jar, and metadata artifacts - it has the md5 and sha1 files only.

The first problem encountered and noted in our Nexus log is:
"Item /org/hibernate/hibernate-jpamodelgen/1.1.0-SNAPSHOT/maven-metadata.xml not found in remote storage."

Will a new one get deployed ASAP?  Is there a different repo location to use/nightly drop?


[0] https://repository.jboss.org/nexus/content/repositories/snapshots/org/hibernate/hibernate-jpamodelgen/1.1.0-SNAPSHOT/

[1] http://snapshots.jboss.org/maven2/org/hibernate/hibernate-jpamodelgen/1.1.0-SNAPSHOT/

[2] https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/hibernate-jpamodelgen/1.1.0-SNAPSHOT/


> Embedded generic types not supported by metamodel generator
> -----------------------------------------------------------
>
>                 Key: METAGEN-29
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-29
>             Project: Hibernate Metamodel Generator
>          Issue Type: Bug
>          Components: processor
>    Affects Versions: 1.0.0-CR-1
>         Environment: Hibernate 3.5.0-CR-2
>            Reporter: Adrian Hummel
>            Assignee: Hardy Ferentschik
>            Priority: Critical
>             Fix For: 1.1.0
>
>         Attachments: bugreport.zip
>
>
> Scenario: I have a @MappedSuperclass defining an abstract entity. This class has a technical primary key and a business identity. The business identity is realized by means of a generic embeddable (e.g. for a Customer class there is a corresponding CustomerId class for its business identity).
> The JPAMetaModelEntityProcessor does generate the AbstractEntity_ class but does only include the primary key field but omits the generic field for the business identity (which leads to subsequent errors when accessing this field using a CriteriaBuilder).
> Attached a mini project with a test case which illustrates the problem. 

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