Samisa, it looks to me as if the branch Sanjaya created so far has only my changes to AXIS2C-675. I think I misread this email the first time to say that you had already written the changes to implement a clone method. Were you intending that the source for axiom_node_clone that serialized/deserialized would be in om_node.c? If so, I'm thinking that's where my draft of an axiom_node_copy belongs, too.
Second question, I don't see a Jira work item open about building a clone routine or an alternative copy routine. It does appear that we could reopen AXIS2C-677 and track the activity there. What do you think? Thanks, Bill -----Original Message----- From: Sanjaya Ratnaweera [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 9:39 AM To: Apache AXIS C Developers List Subject: Re: Issue in using 'detach' for cloning Samisa Abeysinghe wrote: > Hi Bill, Kasun and others, > Thank you all for taking time to explain this problem in detail. > Looking at the ADB use case that Bill has portrayed, I am sure other > users too would be interested in such a case where they can 'get' form > one ADB type and 'set' on another ADB type. > > Lets create a branch for this and try to solve the problem. Bill, > have you already done some work with respect to ref-count? If so we > can start form that. > I can think of the following cases that we can try to fix/implement: > 1. Implement the ref-cout shallow copy mechanism proposed by Bill > 2. Try and implement a deep copy version of detach (so that we can > detach and attach) > 3. Implement a serailize/deserialize based deep copy I have created a branch for this. Here's the url. https://svn.apache.org/repos/asf/webservices/axis2/branches/c/axiomfix/ Thanks ~sanjaya > > I can look into 2 and 3. > > Thanks, > Samisa... > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
