> > So it affects the namespace of the > binding definition, but it shouldn't affect the namespace of the > global elements used by message parts within the portType > referenced by the binding (i.e., what goes on the wire). > In this example the portType is "ns0:HelloWorld" which refers to > global elements in the correct namespace "http:/helloworld" > > So this looks to me like an Axis bug with namespaces for imported > portTypes not being handled correctly. It seems the binding's > namespace is being used to register these operations instead of > the correct namespace as specified in the portType. > > Where in Axis is this registration happening? Which version > of Axis is being used? With this information I could dig around > a bit in the Axis code. >
How, with this generated target namespace, do we intend that the binding operation name is matched with the port type operation name? Simon
