On Wed, Mar 4, 2009 at 2:12 AM, Alex Shneyderman
<[email protected]> wrote:

> Why does not JdbmEntityStore know about its content and how would I
> explain it to him?

You are now on 'slippery slope' territory ;-)

There is a contract between the UnitOfWork and the EntityStores, where
the EntityStore doesn't know anything about the types to be stored
initially, and throws this exception when they need to be informed.
UoW will when getting such exception call a registerEntityType() to
populate such information.
Since the registerEntityType() method is highly serializable and does
not contain any application level types, it is possible to have
EntityStores remotely that does not have any 'application specific'
configuration or classes.

Cheers
Niclas
-- 
http://www.qi4j.org - New Energy for Java

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to