I'm just wondering what is the best design pattern to used OBJ in a ejb environement. I'm really interesting to receive your feedback about different experiences in this area.
The first solution can be : session bean wich is using direclty OBJ as a persistence manager. Entity beans are completly ignored in this case. Is it make sense for you ? In this case, How can I cache my "business object" on the server ? with a cache, what is your solution for the database synchronisation ? The second solution can be : BMP based on OJB like samples provide with OBJ. What about the entity bean granularity ? How to define relationship between business component (on the entity level or OBJ level) ? All experience comments are welcome and will be use for my own decision. Thanks in advance, Christophe -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
