Simon,
I appreciate the response. If you know, how do I get Axis to not insert that
prefix when it auto-generates the WSDL? Is it a bug, and should I submit a
new bug entry? Or is there a deployment/configuration mechanism that will
prevent this?
Thanks again,
Donnie
-Original Message
Simon,
I appreciate the response. If you know, how do I get Axis to not insert that
prefix when it auto-generates the WSDL? Is it a bug, and should I submit a
new bug entry? Or is there a deployment/configuration mechanism that will
prevent this?
Thanks again,
Donnie
-Original Message
In my
experience, I found that it was necessary to circumvent the sandbox restrictions
when using axis from an applet. That means signing the requisite jars ar least.
I also set my own security manager for convenience sake.
Again,
based on my experience, and depending on what one wants an
Jay,
Thanks. The architectural decision
to use Axis was not mine to make. That being said, Axis being a web based client
server technology, it should have been made to work in an applet -first-
IMO.
Having any web app client
-required- to download libraries is extremely poor desi
Jay and Jay,
IF you really want to help othersIf you see a bug, log a bug
report. If you can, please submit a patch too then it will get fixed
faster. FYI, we are very close to 1.2 Final, so any help in fixing
issues like these is appreciated.
thanks,
dims
On Sat, 1 Jan 2005 13:14:07 -0500,
Hi,
I want to publish a java method as an axis-1.1 webservice, which throws
an exception. The exception should be mapped as a soap-fault. So far so
good.
But is it possible to customize the elements inside the soapenv:Fault
element?
The current response (in case of the exception) is like this:
