[
https://issues.jboss.org/browse/WFLY-9878?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-9878:
------------------------------------
Years ago, we had this problem but I'm not aware of it currently happening in WildFly
11+. I do know that a very simple unit test is working
[
https://github.com/wildfly/wildfly/tree/master/testsuite/compat/src/test/...],
which has the persistence.xml hard coded as a string variable in the test:
{code}
private static final String persistence_xml =
"<?xml version=\"1.0\" encoding=\"UTF-8\"?> "
+
"<persistence
xmlns=\"http://java.sun.com/xml/ns/persistence\"
version=\"1.0\">" +
" <persistence-unit name=\"hibernate3_pc\">" +
"<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>"+
" <description>TopLink Persistence Unit." +
" </description>" +
"
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>" +
" <properties>" +
" <property name=\"jboss.as.jpa.providerModule\"
value=\"org.eclipse.persistence:test\"/>" +
" <property name=\"eclipselink.ddl-generation\"
value=\"drop-and-create-tables\"/>"+
" </properties>" +
" </persistence-unit>" +
"</persistence>";
{code}
I'm not sure if the org.eclipse.persistence.internal.jpa.deployment.ArchiveFactoryImpl
logging would help identify the root cause or actually debugging the
org.jipijapa.eclipselink.JBossArchiveFactoryImpl (with your application deployment). If
you want to try to debug, I can give you some pointers to make sense of how some of the
code (e.g. acts as a bridge between the WildFly virtual file system (VFS) and EclipseLink
ArchiveFactoryImpl).
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#JPAReferen...
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)