I was just asked to take a look at this product with an eye towards "possibly" moving there. We have spent an awful lot of time painstakingly designing a set of business objects that reflect what we do. We have also written several applications using these.
Thes objects are designed as java objects/classes. We have a robust set of applications that use them. I have written a homegrown data access level for these objects and am now looking for an object to relational solution (ala Hibernate, XORM, different JDO implementations etc). The thing is we "have" the app, we "have" the design, and we live with java. Now my question is this. It appears there are tools in Cache to project "Cache Objects" to jave, or to import from UML or whatever, and to write DDL. This sort of approach is almost "Cache centric". What i would like to do is take my java objects and generate the appropriate "Cache Objects" from it, then perhaps write the layer where our objects talk to cache objects. What i was hoping i didn't have to do was to redesign all the objects from scratch. Does such an approach exist? Anybody out there start from where i am and have suggestions on how to bridge into "Cache" from our existing java? Our java application and domain is our system, the database (while very very important), in the end should be some what portable. Or another words, we view our application (java) using Cache, not Cache using java. any suggestions?
