Sanjaya, you raise a question that I was going to ask Dinesh. In my mind, I see Jira 675 as a bug. For some xml document trees, detach generates a structure that is later unusable by the adb stubs that depend on it. As such, it could still be a candidate for inclusion in 1.3. And I see our other two activities, an axiom_node_copy_tree and axiom_node_clone_tree routines that solve some other, similar issues for the higher level apps as a new feature, isolated and relatively safe, but still at this point warranting exclusion from any current release activity as a new feature.
But, it's not my decision; I think it's up to Dinesh. I did notice that you had built a branch, and I extracted a copy, although I think I grabbed a copy by revision number. I will be seeking today to take my axiom_node_copy_tree routine and include it there. Thanks, Bill -----Original Message----- From: Sanjaya Ratnaweera [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 8:22 AM To: Apache AXIS C Developers List Subject: Re: Issue in using 'detach' for cloning Hi bill, > I have created a branch for this. Here's the url. > > https://svn.apache.org/repos/asf/webservices/axis2/branches/c/axiomfix/ > I have applied your patch in jira issue 675 to this branch. It failed in a one file. (axiom/include/axiom_element.h). It had only api doc comment changes. The rest was ok. Thanks ~sanjaya --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
