Ashok,
well it seems that Axis has a problem when you dynamically
(programatically) setup the handler chain as it is done in the JAX-RPC
testcase. The Axis code may not initialize some internal parameters or
properties correctly if you don't use deployment files. Because
of the non-initialized (or wrong initialized) properties it is not
possible to replace the original content of the request with the
security enhanced SOAP request - thus your client will never send a
correct SOAP request with security elements.
Some guys over at the Axis development are just trying to figure out
what is going on.
I will also do some more testing at WSS4J and try to get some more info
about the problem. Already tested some ways for a workaround, but
without success yet.
Regards,
Werner
Ashok Shah schrieb:
Hello Werner,
Second NOTE: recently we discovered a problem in Axis
that could cause problems if you use the fully dynamic option.
Thus I would advise to use deploymentfiles to setup
the handler chain, other parameters like action,
user, etc. can be set via the configuration properties.
I was wondering if you could brief me on the problem that was
discovered in using the dynamic deploymentfiles option. It is critical
for our system to not use configuration files. Whole environment is
setup from the program including the handlers, actions and other
required paramets, including on the client side.
Apperericate your help.
Thanks,
Ashok.
