Niclas Hedhman wrote:
Yes, this requires some thinking.
I think you also realize that this is not a problem for REST URLs
only. As you pointed out, EntityStore.getEntityState() takes the type
as input and if it has been refactored, it is 'gone'...
Something like that, yeah. It might be that getEntityState() should
simply take id as input, and whatever it was stored with should be the
type, and not what the client suggests it is.
It also kind of feels odd that we need to involve the EntityStore in
the resolution of schema version. What happens if "type" is not known
to the EntityStore at all? What is affected and currently needs the
type information?
Exactly. Could we put EntityTypes and schema handling in a separate
service perhaps?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
