On Wed, Mar 25, 2009 at 10:20 AM, Rickard Öberg <[email protected]> wrote:
> Then the type can change as much as it wants, and it will still work. The > problem here is that the server-side of this will have to call > EntityStore.getEntityState() which takes a QualifiedIdentity as input, which > includes the type. So that's no good. > This requires thinking. Any ideas? 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'... 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? Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
