DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-802
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Ales Justin
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
DataNucleus Core

Allow for custom (container / env) scanning for entity classes

Created: 17/Jan/12 12:30 PM   Updated: 06/Feb/12 10:13 AM   Resolved: 20/Jan/12 10:23 AM
Component/s: Configuration, MetaData
Affects Version/s: 3.0.5
Fix Version/s: 3.0.6

File Attachments: 1. Text File NUCORE-802_core.patch (10 kB)

 Description  « Hide
Currently we're limited to exploded deployments for initialization scanning of entity classes.
It should be possible to pass-in some-sort of Scanner instance from container / env, which would know how to do this better, more optimized.

Sort Order: Ascending order - Click to sort in descending order
Ales Justin added a comment - 19/Jan/12 11:05 PM
Where JPAEntityManagerFactory:750 (in api.jpa) needs to be changed to use this new over-loaded method:
* nucleusCtx.getMetaDataManager().loadPersistenceUnit(unitMetaData, null, props);

Andy Jefferson added a comment - 20/Jan/12 10:23 AM
SVN trunk now has an adaptation of your patch, thanks.
I've changed the following :-
* scanner interface is now MetaDataScanner
* scanner interface has method scanForPersistableClasses(...)
* no need to pass in properties into MetaDataManager method call since it has "nucleusContext" which provides access to all persistence properties.