Hi All, I have noticed OModel serialization issues before. The only problem is that OModel refactoring is not so important at my point when use ODE. So I did not think it over and somewhat ignored it. However, I'm still interested in it. I think I could work on it, and here I'd like to talk about my understanding on the issue.
In my view, OModel gives a compiled representation of BPEL elements. The OModel objects are serialized for permanent store and exchange. It relies on java serialization mechanism which is not flexible enough, so problem occurs when we need evolve the existing OModel classes or new OModel classes or share objects in cluster. The candidate new serialization solutions are mainly in two ways. First, we could store a Map<String, Object> and wrap all data that is currently stored in field in this Map. And the java serialization mechanism can still be used. Another way is that we employ a new serialization mechanism like Jackson. Another important problem is that how we can migrate to the new OModel. And as Tammo says, is the most difficult part. Roughly thinking, it involves many sub-projects like compiler, store, dao and underlying database. But I konw little about the details. This is my preliminary understanding on OModel refactor. Hoping for suggestions and corrections. Should we open a new thread for OModel refactor topic? Thanks, Zhen
