Hi,
I want to try an issue with OJB and would like to know if anyone had do it:
1) Client side. (note: this application don't have and don't know about OJB only know about the Object)
1.1) request the server for an object.
2) Server side. 2.1) receive a request to load an object. 2.2) load this object from PB. 2.3) serialize this object to client.
3) Client side. 3.1) receive and deserialize the object. 3.2) make changes on this objects. 3.3) serialize this object to server to be updated.
4) Server side. 4.1) receive a request to update an object. 4.1) open a PB transaction. 4.2) update the object. 4.3) commit PB transaction. 4.4) returns a serialization of this new updated object to client
5) Client side. 5.1) receive and deserialize the object. 5.2) and says to user object updated. 5.3) the end.
Then troubles to be solved with this in OJB with PB are:
For step 2.3, since the client don't know NOTHING about OJB how are you solved problems with dependencies of interfaces and classes for collections, like RemovalAwareCollection. before serialization created a new Vector and put all elements from RemovalAwareCollection in this new Vector and changed the reference to this, then serialize? or OJB provides a better way?
For step 4.2, load the object see what has changed in serialized object and change in transaction object, or exists a method like makeDirty (from OJB ODMG) that do this in PB? if yes how OJB will control the RemovalAwareCollection that in serialized object, is now simply a Vector?
TIA
Cl�vis
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
