Yep - I guess I answered my own question of how to manage the namespace.
Since I am not really
interested on using the namespace on the client side other than building
local directories to store the
stubs, I can simple use the --package option to generate what I need.
If there is any other (more efficient and correct method) out there by
all means stop me ! ;)
Thanks
Demetris wrote:
Hi all,
I intercept and transport the outgoing HTTP GET request to a remote
axis container/engine
over a p2p overlay. I reissue the GET command using HTTP libraries on
the remote side and the
URL I sent always has the http://127.0.0.1:8080 in it .. however the
WSDL I get back does not
always (and I say does not always because it is not consistent over
identical reps) contain this
local address in its namespace:
ex. <wsdl:definitions
targetNamespace="http://cypress.ne.uk:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9";
instead of
ex. <wsdl:definitions
targetNamespace="http://127.0.0.1:25718/axis/services/remoteBooks73862E4EF09047ABB172814D14F915A9";
etc.
Why is this the case and should I force the namespace to be what I
want on the client side by
using the --package command as a safeguard?
Thanks much
Demetris
