Hi, It seems that there is chance this will become a great product. Just like GemStone?
2009/4/17 Niclas Hedhman <[email protected]> > On Thu, Apr 16, 2009 at 8:52 PM, tao wen <[email protected]> wrote: > > > How about deployment and migration? If all server components are generic, > > one pre-condition to that would be there is no need to deploy new class > > definitions or migrate to higher versions, that means to be generic must > not > > be static typed as java. > > There are so many layers to that question. > > The client code will change types, is statically typed and so forth, > and it interfaces with UnitOfWork and supporting systems. The > UnitOfWork will map that static type information to runtime data, > store the type information needed for future migration. But the layers > below (i.e. EntityStores) don't deal with any of the actual types used > in the client code. So, yes, the underlying entitystore has no > understanding of the types being used at the client layer, and No it > is not abandoning Java's static type system, it is still statically > typed at the client level. > > So, in case of old data is used in a new version of the client, the > client programmer provides a 'converter' for how to get from version > FAUGYHBVSFYHUYUY to version UYHGCFUYGUHWB, and the UnitOfWork will > invoke that prior to the placement of the data into the statically > typed Entities the client sees. > > Does that answer your question? > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
