Me!

Yep, I resolved that problem with Namespace optimization – basically I had to apply mentioned patch and upgrade Axiom to version 1.2.8. The error message I got previously was connected with old Axiom and they way how it was called from Axis 2. When you are using Axiom 1.2.7 you must change way how you are calling Axiom, see below – the second parameter has to be null (but this is the root of problems):

param.save(builder, null, xmlOptions);

Using original idea from patch is to call that method like this:

param.save(builder, builder, xmlOptions);

but you must using the latest Axiom version which is 1.2.8. Problem with that solution is that we are using home made dependency management tool and it isn’t so easy to hack central repo ;-)

Right now I’m looking into other solution – handlers! Axis 2 define a special way to connect your custom code with internal mechanisms, but it isn’t so clear for me how I could do that :P