Have we explored storing a specific Parameter on the AxisOperation that told them an operation was not a user-defined operation? I know there is very little chance of a collision with a user-defined operation, but there is still a small chance. Is storing a parameter on the AxisOperation instead a feasible option?
Michael Rheinheimer <[EMAIL PROTECTED]> wrote: Hi, The sandesha team has requested that a custom prefix be included in the QNames of the anonymous operations (anonOutInOp, etc) to differentiate axis2-originated anon operations from customer-defined operations. Is it simply a matter of adding a prefix to the QName definitions in kernel code: org.apache.axis2.client.ServiceClient? Doing so caused no errors in my testing, but I am certainly capable of overlooking something, and this is core kernel stuff, so please help me out! See related Jira: https://issues.apache.org/jira/browse/AXIS2-3730 Thank you much! mike __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
