I'm currently working on using different EOModels to access diffrent
databases, for scalability reasons. Model A only has to-one relations
to Model B, and Model B is selfcontained, it doesn't reference any
entities in model A (Well there is one exception, but that will go
away).
Relations accross models seems to be working ok, excepts for for
cases where the referenced entity is part of a inheritance hierarchy
and is a non-leaf entity. In this case i get an exception with the
following message from EOF.
"An empty fault could not be created because the object's class could
not be determined."
I guess somehow EOF cannot determine the actual entity to use (having
only the Super entity name). The funny thing it that it works when
running both models on a single database. The exception is by the way
thrown before any database fetches are done, so the conclussion, to
throw the exception, from EOF is based on model info only.
Does any one know:
1) Is this a bug -i can't currently think of reason why two
database context willl hinder EOF to construct the correct sql to
fetch the actual row in the database.
2) Or is there a reason why this is not possible?
3) Or should i do something special to make this, change something
in the model, implement som delegate, create my own subclass of
something?
Any input to this will be much appreciated.
BTW: it is single table inheritance and all the entities of the
inheritance hierarchy a placed in the same model (A).
