Resolve JDOClassDescriptors on the filesystem

Patch also includes changes in the MappingLoader interface. Is there a specific place/package to put a testcase (e.g. cpactf)? I would therefor love to add a testcase.

I forgot to add the addPackage functionality to this task. If package added, a cdr file, equivalent to xml should be consulted.

I forgot to add the addPackage functionality to this task

Don't worry, we can always add this at a later time. I'd like to get above patch in a.s.a.p. as I've got all this Spring code ready that has a dependency on this change.

The current JDOClassDescriptorResolver prioritizes ClassDescriptors on the filesystem. Hence, there is no way, not to use a ClassDescriptor and use a mapping instead. Maybe we should consider, whether an external Resolver with added classes was set in the JDOManager.

Lukas, tests that do not require database access should be placed under cpa/src/test/java.

If you first consult mapping before searching for ClassDescriptors on the filesystem you should be fine without the need to set external Resolver on JDOManager.

Actually, I have seen the very same problem even in a case where there's mapping only, as all of a sudden no mapping can be loaded anymore (NPE on loading a field mapping). I am actually debugging to see what's going on.

In general, I think that consulting with the mapping first should be the correct approach for the time being.