[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-126) Configuration option for custom EntityResolver

[Christian Bauer (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-126?page=comments#action_24200 ] 

Christian Bauer commented on EJB-126:
-------------------------------------

The initial use case is definitely solved, we now detect classpath:/ prefix in the DTD in Core 3.2. This should probably be downgraded as a very minor feature then.


> Configuration option for custom EntityResolver
> ----------------------------------------------
>
>          Key: EJB-126
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-126
>      Project: Hibernate Entity Manager
>         Type: Improvement

>   Components: EntityManager
>     Reporter: Christian Bauer

>
>
> The only way to set a custom EntityResolver is the Hibernate Configuration API. Max already added an option to the Ant task and tools. Now I need the same for EntityManager, otherwise nobody can use XML mapping files with includes.
> Should we add it as a regular Hibernate configuration option or only as an additional EM bootstrap property?

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira