Ann, Let's figure out a way to get out of this loop. No, i don't think that we should add code just because it does not break any existing things...
How about we start a branch for this work? I'd personally be satisfied about moving to trunk when i see a test case in this branch that illustrates that when deserializing the MC, it plays well with the existing hierarchy and does not create any extra objects unnecessarily. Once you illustrate that, we can move the code to trunk. Are you ok with this plan? Am sure sanjiva/chamikara/others can help formulate other scenarios that the ser/deser mechanism should work "properly". thanks, dims On 12/18/06, David Illsley <[EMAIL PROTECTED]> wrote:
>c) Sorry for being blunt, but I honestly think, that this proposal is being pushed so hard bcos it works with some IBM internal product. You're right it works with an IBM project (FWIW it also works with Sandesha2) which is why I know it works and why I believe it's very unlikely to break pure Axis2. I'm not philosphically attached to any particular way of implementing this function, but I've seen it working so I thought I'd jump in and comment when I thought the discussion seemed more philosophical+process related that technical. Apologies for any ill-will my comments have caused, David -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
