File tree Expand file tree Collapse file tree 1 file changed +17
-0
lines changed
documentation/src/main/docbook/devguide/en-US/chapters/osgi Expand file tree Collapse file tree 1 file changed +17
-0
lines changed Original file line number Diff line number Diff line change 347
347
considerations, collision protections, etc.
348
348
</para >
349
349
</listitem >
350
+ <listitem >
351
+ <para >
352
+ Some containers (ex: Aries) always return true for
353
+ <literal >PersistenceUnitInfo#excludeUnlistedClasses</literal >,
354
+ even if your persistence.xml explicitly has <literal >exclude-unlisted-classes</literal > set
355
+ to <literal >false</literal >. They claim it's to protect JPA providers from having to implement
356
+ scanning ("we handle it for you"), even though we still want to support it in many cases. The work
357
+ around is to set <literal >hibernate.archive.autodetection</literal > to, for example,
358
+ <literal >hbm,class</literal >. This tells hibernate to ignore the excludeUnlistedClasses value and
359
+ scan for <literal >*.hbm.xml</literal > and entities regardless.
360
+ </para >
361
+ </listitem >
362
+ <listitem >
363
+ <para >
364
+ Scanning does not currently support annotated packages on <literal >package-info.java</literal >.
365
+ </para >
366
+ </listitem >
350
367
<listitem >
351
368
<para >
352
369
Currently, Hibernate OSGi is primarily tested using Apache Karaf and Apache Aries JPA. Additional
You can’t perform that action at this time.
0 commit comments