You should create DTO for your object graph. On 5/7/07, Tom Pasierb <[EMAIL PROTECTED]> wrote:
Hello,I'd be grateful if some of you guys could help me with a problem I have. I'm developing an RCP app which communicates with my server through webservices (xfire). Certain dialogs get the data from the server side, show it to the user, user modifies the data and it is to be sent to the server and saved. The problem is that the objects behind the dialog are entities with properties of type Collection. Objects in the collection have a back reference to their parent. This is a circular graph of objects. I know that XFire cannot handle these. I would like to know how I can solve it, I know the graph should be flattened. Is there a mechanism in Xfire that would enable me to do some work on the object before it is serialized to xml (I could flatten it there) and again do some work after it's deserialized on the other side (where I could restore the object to the original) ? Maybe there is a better way to do it? --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
