Issue Details (XML | Word | Printable)

Key: NUCCORE-501
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Andy Jefferson
Reporter: Marco Schulze
Votes: 0
Watchers: 0
Operations

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

Support interfaces without implementation

Created: 01/Apr/10 12:35 PM   Updated: 26/Apr/10 03:37 PM   Resolved: 21/Apr/10 09:16 AM
Component/s: Configuration, Java Types, Persistence
Affects Version/s: 1.1.3, 2.1.0.m1
Fix Version/s: 2.1.0.m2


 Description  « Hide
DataNucleus supports dynamic schema extension (i.e. new persistent classes being added to an existing schema later). Thus it is a prime choice for highly modular applications with some plug-ins providing (abstract) frameworks and others providing implementations. Unfortunately, though, DataNucleus expects at least one implementation being known when an interface is used as field type in a persistent class. Hence, a framework which makes use of interfaces in 1-n- or 1-1-relations currently *must* provide at least one implementation.

It would be a good feature, if DataNucleus did not have this requirement anymore and accepted situations in which no interface implementation is known (yet).

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 14/Apr/10 07:57 PM
Use SVN trunk with persistence property
datanucleus.permitReferencesWithNoImplementations=true

Works for me with (very) limited testing (i.e SchemaTool) on a 1-1 relation. Will ultimately remove the persistence property when it has been thoroughly tested

Andy Jefferson added a comment - 21/Apr/10 09:16 AM
Marking as fixed. Renamed the persistence property to
datanucleus.store.allowReferencesWithNoImplementations
and added to docs.