Casper Bang wrote: > Yeah but isn't that a fundamental problem, not unlike how you version > a service so not really a particular OO issue. Well, it seems like the problem is more pronounced in OO systems than in the relational world. > But since we can't > create a new immutable schema/endpoint daily, there are techniques > which allows us to at least run longer within a given major contract > spec, XMLDecoder/Encoder being one of them. > We were actually implementing things to manage schema migration in the object database world. But by then, no one wanted that technology. > Until versioning is treated at the language level, I don't see how > this can be handled any different. Well, I think it actually needs to be part of the runtime also. In fact persistence (which is effectively the same problem but worse) should be part of the runtime system. In many cases I'd advocate pulling code out of the JVM to implement it in Java. In these cases it seems more appropriate to place some of it back into the JVM. As easy as JPA has made persistence, it is nothing like using an OODBMS.
Regards, Kirk Speaking @ devoxx Speaking @ jfokus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
