Title: RE: Authorizing users in Axis
In general, I think you should steer away from passing credentials in each and every method. A good design pattern is to authenticate your end user using some 'security service' that, if authentication succeeds, would produce a token that would be passed i
Some good reasons to use WSDL:
1. WSDL aids interoperability. You can post your WSDL to a directory and
any Web Services developer in any technology (Java, .NET, etc.) will
have everything they need to build a client to invoke your service
(assuming it conforms to established conventions/standard
See WS-I Basic Profile rules below:
R2201 A document-literal binding in a DESCRIPTION MUST, in each of its
soapbind:body element(s), have at most one part listed in the parts
attribute, if the parts attribute is specified.
R2210 If a document-literal binding in a DESCRIPTION does not specify the
Axis is JAX-RPC compliant which means that you can develop Doc/Literal Web
Services where you need not ever deal directly with XML. Rather you can
work directly with Java stubs and server-side skeletons. Axis will marshal
and unmarshall your Doc/Literal SOAP message for you using Java classes
gene
