[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5026?page=c...
]
Andreas Joseph Krogh commented on HHH-5026:
-------------------------------------------
Hi Emmanuel, nice to see communication works around here:-)
I did read your post this weekend when trying to port some infrastructure-code to JPA2
(using Hibernate of course) without much success. I've never actually used the
<jar-file> element in persistence.xml for anything before as I like to configure all
using Spring, but are you telling me that it's possible to split up *one*
persistent-unit across several jar-files using this technique? I really need all entities,
spread around different jar-files in different maven-modules, participating in the same
transaction.
I also ran into issue HHH-4870 which I worked around setting
hibernate.ejb.metamodel.generation=disabled as suggested, although I'm not sure
exactly what the effect of that is.
Ability to customize Scanner strategies
---------------------------------------
Key: HHH-5026
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5026
Project: Hibernate Core
Issue Type: New Feature
Components: entity-manager
Affects Versions: 3.5.0-CR-2
Reporter: Emmanuel Bernard
Assignee: Emmanuel Bernard
Fix For: 3.5.0.Next
hibernate.ejb.resource_scanner
By default, Hibernate EntityManager scans itself the list of resources for annotated
classes and persistence deployment descriptors (like orm.xml and hbm.xml files).
You can customize this scanning strategy by implementing
org.hibernate.ejb.packaging.Scanner. This property is used by container implementors to
improve integration with Hibernate.
Accepts an instance of Scanner or the file name of a no-arg constructor class
implementing Scanner.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira