You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2013/05/16 06:43:16 UTC
[jira] [Commented] (ARIES-1045) Consider allowing
excludeUnlistedClasses to return false
[ https://issues.apache.org/jira/browse/ARIES-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659216#comment-13659216 ]
Tuomas Kiviaho commented on ARIES-1045:
---------------------------------------
I'm not part of the project but here are my two cents because a month ago I just wrote a OSGiScanner for Hibernate 4.3.x myself and used Aries JPA as backend.
There is at least ManagedPersistenceUnitInfoFactory that you can hook into using {{org.apache.aries.jpa.container.properties}} and using {{org.apache.aries.jpa.container.ManagedPersistenceUnitInfoFactory}} just like you would with J2SE META-INF/services contract. This was a nice way for me to get container properties out of persistence provider service registration which in turn gave me possibility to use and scanner instance instead of class name reference.
To use this feature properly I'd be introducing a separate hibernate-aries bridge.
--
Tuomas
> Consider allowing excludeUnlistedClasses to return false
> --------------------------------------------------------
>
> Key: ARIES-1045
> URL: https://issues.apache.org/jira/browse/ARIES-1045
> Project: Aries
> Issue Type: Improvement
> Reporter: Brett E. Meyer
>
> Hibernate is in the middle of finalizing support for Enterprise OSGi JPA environments -- many thanks to [~timothyjward] for assistance. I primarily use Aries as the container for testing.
> Tim pointed out that Aries always returns true for PersistenceUnitInfo#excludeUnlistedClasses(). Although I think I understand the initial reasoning behind that, I'd request that it return the real value of "org.apache.aries.jpa.exclude.unlisted" (ie, "<exclude-unlisted-classes>").
> Hibernate supports scanning to find non-explicitly listed classes, mapping files, orm.xml files, etc. With Tim's help, we implemented an OSGi-specific scanner to search BundleWiring resources. However, we really need to honor the real value of "<exclude-unlisted-classes>" before we attempt that.
> It would be great if supporting entity scanning was left up to the JPA provider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira