[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5026) Ability to customize Scanner strategies
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5026?page=c...
]
Andreas Joseph Krogh commented on HHH-5026:
-------------------------------------------
Does this affect HHH-4864 in any way, making it possible to merge persistent-units spread
over multiple modules/jars? Any sufficiently modular application would be designed this
way so it's very surprising Hibernate/JPA2 doesn't support this "out of the
box".
I work on 2 projects relying on the approach described here
http://ancientprogramming.blogspot.com/2007/05/multiple-persistencexml-fi... and
I don't see an easy migration-path to JPA2.
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