[jboss-jira] [JBoss JIRA] (WFLY-10381) AttributeConverter injection fails with EclipseLink if deploy-on-startup = true

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578105#comment-13578105 ] 

Scott Marlow commented on WFLY-10381:
-------------------------------------

[~jlukas] Any thoughts on this (WFLY-10381) issue?  

IMO, I think that EclipseLink implementing [https://github.com/javaee/jpa-spec/issues/83], could help avoid the need for the eclipselink.deploy-on-startup workaround.  


> AttributeConverter injection fails with EclipseLink if deploy-on-startup = true
> -------------------------------------------------------------------------------
>
>                 Key: WFLY-10381
>                 URL: https://issues.jboss.org/browse/WFLY-10381
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 12.0.0.Final
>            Reporter: Rich DiCroce
>            Assignee: Scott Marlow
>
> As of 2.7, EclipseLink implements JPA 2.2 and therefore supports injection into AttributeConverters. Injection fails silently if the eclipselink.deploy-on-startup PU property is set to true, because the BeanManager is not available yet when EclipseLink tries to instantiate the AttributeConverter.
> Workaround: don't set the deploy-on-startup property.
> It would be nice if this could be made to work, but I'm guessing it will be a chicken/egg problem of dependencies between CDI and JPA. So if it can't be made to work, it would be good to at least detect that the PU property has been set, and warn about it in the log.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)