Tibco XML Schema namespace usage memo

In tibco, It is very common to transmit information in XML format. For example, we provide a WebService WSA for someone to call. the WSA method wsaf input references an XML schema projectbox, after this wsaf is called, we use the soapeventsource component to obtain the information input by the other party and provide it to other components, such as $ soapeventsource/inputmessage/NS1: projectbox/NS1: project_id.

The preceding string allows other components to obtain the project_id, $ soapeventsource/inputmessage/NS1:Projectbox/NS1:Project_id.

In the schema of the projectbox I defined, I did not define the NS1 information. This was generated by tibco. When I changed the wsaf input reference to another schema projectbox2, I found that the string provided by the soapeventsource component to other components is: $ soapeventsource/inputmessage/NS5:Projectbox/NS5:Project_id.

When I have sent the input information of soapeventsource to many components, I modified the schema referenced by the input of wsaf, so I have modified many places, this is clearly not what I want. Is there any solution?

I guess NS1 and NS5 are directly related to namespaces. At that time, many things in tibco were related to namespaces. After a series of explorations, tests, and elimination, finally, I found the schema of projectbox2 (tibco's schema editing is really hard to use ),

Focus on targetnamespace of projectbox2 Schema, I changed the targetnamespace to the same as the projectbox schema, and re-referenced the wsaf input to the projectbox2 with the targetnamespace modified (required in this step, after the targetnamespace is modified, the original reference link has expired.) test it. $ soapeventsource/inputmessage/NS1:Projectbox/NS1:Project_id
It is feasible, and it does not conflict with projectbox (it has not been tested whether there will be conflicts under the same process, but different processes are sure they will not conflict). It is a perfect solution to this problem.

Random values such as NS1, ns2-, pfx1, and pfx2 automatically generated by tibco, and attributes of the referenced XML SchemaTargetnamespaceThere is a direct relationship.
For targetnamespaceThe differences between xmlns and xmlns are also clear. This is simply the case for external use and internal use.