Could you add a unit test?

Could you add a unit test?

OK,I will do this

@whatever098 could you give some background on why adding the unused extra namespaces is useful? I'm struggling to see how this is useful.

@pjfanning When we save the java code generated by xsd as xml, we need this method to set the namespace

XMLBeans adds the namespace declarations that it needs. I'm against merging this. What if someone adds an 'extra namespace' with the same prefix as one that XMLBeans generates for its own needs? We've gone 20 years without needing this support.

Provide a very detailed example of why you need this - something that fails without this support - or I will remain against adding this.

You are free to fork XMLBeans and add whatever you like to your fork.

@pjfanning Let me explain the reason in detail. When I generate a jar with an xsd containing some namespace(such as
uof.zip
), the xml file written using the jar does not have the namespace I need and cannot be opened normally. This test process cannot be expressed by unit testing. If you need me to demonstrate it with code, I will upload a use case code package tomorrow to demonstrate why I need to use extra namespace.

I will not merge this unless there are checks so that the extra namespaces do not clash with the namespaces that XMLBeans generates for itself.

Actually, I think we should abandon this and work out why XMLBeans does not generate the correct namespaces in the 1st place.

You are right,I will try

@pjfanning I review my modified and found using setSaveImplicitNamespaces can achieve my appeal, but using this method will traverse the XML files twice, this could lead to problems in the performance of some of the scenes, so now I will use setSaveImplicitNamespaces moment, There may be time later to commit changes to the PR to add some checks during my free time.By the way, can you deal with the pr #19 as soon as possible, this matters to me.