Your question drives to the heart of one of the key dividing lines in the SOAP standard today: RPC versus document style SOAP messages. In document style, you can think of any given message (a request or a reply) as having only one "parameter", but that parameter is a complex data structure usually.
When using document style messages, there's no real reason to give a name, because there's only one "parameter", and it can't be null (so it's type can be determined directly from the instance you pass). This is the most fundamental way to transmit SOAP messages.
RPC style is designed to fit easily with programming languages by making each parameter appear separate. In reality, however, all that really happens is that each parameter is put as a member element of an "artificial" data structure which is transmitted document style. So, Axis requires that you give it the parameter names and types so it can (internally) construct this artificial data type to be transmitted.
One recommendation for you is that, instead of coding call objects yourself, you might want to consider starting from WSDL. If you start with WSDL, Axis includes a code generator that will generate all the necessary code to wrap around the underlying Axis Call objects (so you don't need to do all the manual infrastructure coding and can instead focus on the business value of your application).
Dig Deeper on Topics Archive
Related Q&A from Daniel Foody
Daniel Foody defines end-to-end security and discusses the different parts of security to consider. Continue Reading
Dan Foody discusses the capability of using Web services for ASP applications. Continue Reading
Daniel Foody discusses the "find-bind-execute" paradigm and secure service directories. Continue Reading