Hello Li
the biggest problem with a contract is you are bound to fixed record
doc-literal-encoded has been around for 7 years and has been deployed numerous
times on numerous production sites
Here is a good whitepaper to read on the advantages of doc-literal over RPC
http://www.ibm.com/develope
We are trying to apply message-level security to our Web Services -
encrypting and singing the SOAP messages.
Our web service is deployed on Oracle WebLogic 10.3 application server. It
complies with standards:
* WS Security 1.1
* WS Security Policy 1.2
* WS Policy 1.2
For im
I have been puzzled by this issue for long time. Seams like at this point,
using contract-first approach is the only solution for now.
But it will still be very very helpful if something can be done so
code-first approach can work too. Axis1 definitely worked. I can imagine
lots of people are usin
Il 17/02/2010 3.53, glopezm ha scritto:
Any thoughts/experiences with a similar issues with axis2?
I use contract-first approach. My user exceptions extend Exception and
have a field called faultMessage with getter getFaultMessage and setter
setFaultMessage. The constructor prepares the fault
