[jboss-jira] [JBoss JIRA] (WFLY-9878) EclipseLink Entity Scanning broken in Wildfly 11

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-9878:
------------------------------------

jboss.as.jpa.providerModule is the name of the persistence provider module (default is org.hibernate), you do not need to set that, as it will be derived from the provider=org.eclipse.persistence.jpa.PersistenceProvider.

I assume that some code change is likely needed, so to account for the difference between the simple unit test and your application.  Most likely, something is going wrong in the org.jipijapa.eclipselink.JBossArchiveFactoryImpl class, would be my guess.  I suppose that something in org.eclipse.persistence.internal.jpa.deployment.ArchiveFactoryImpl may also be going wrong.


> EclipseLink Entity Scanning broken in Wildfly 11
> ------------------------------------------------
>
>                 Key: WFLY-9878
>                 URL: https://issues.jboss.org/browse/WFLY-9878
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 11.0.0.Final
>         Environment: Enterprise Maven Project
> Wildfly 11
> Eclipse Link 2.7.1 (2.6.3 and 2.64 were also tested)
>            Reporter: Alessandro Moscatelli
>            Assignee: Scott Marlow
>             Fix For: 12.0.0.Final
>
>
> Following :
> https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferenceGuide-MigratingfromEclipseLink
> When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a  :
> Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type
> If I list such entity in persistence.xml the error is gone and the entity is persisted.
> Inside standalone.xml I used :
> <system-properties>
>    ...
>    <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/>
> </system-properties>
> Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ?
> I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa.
> I tried several combination of older jipijapa and eclipselink versions without success.
> I have about 130 entities in my probject, I'd REALLY love not to enlist them all.
> My persistence.xml :
>     <persistence-unit name="optoplus">
>         <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
>         <jta-data-source>java:/jdbc/db_optoplus</jta-data-source>
>         <exclude-unlisted-classes>false</exclude-unlisted-classes>
>     </persistence-unit>



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