[
https://issues.apache.org/jira/browse/ARIES-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659614#comment-13659614
]
Brett E. Meyer commented on ARIES-1045:
---------------------------------------
I know there are ways around the issue, as Tuomas points out, but they all
require tricks specific to Aries implementation details. For JPA providers
(like Hibernate) that do not want to introduce dependencies on any specific
container, supporting excludeUnlistedClasses is important.
> 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
