Web Services.........XML schema of operation parameter?

Question

This is a generic question :)
If my implementation fucntion is accepting a XML how can we embed the schema of the input XML in the WSDL so that it can be discovered by user/client?
Is it possible to define the input XML schema in the element binding? and how?
In contrast if the implementation function is accepting primitive types as input data , the how does the user/client encode(XML marshall) the information in his post or soap message so as to be understood by the web service.
Or
the user can directly write a client program and pass primitive parameters,marshall unmarshalling is done automatically?
No need to worry about how the data is carried in the post and soap messages?
Also what are the differrent ways in which a web service can be used and consumed?
If the user doesnot want to write a client program, but directly pass an http post or soap message, how will the user know how to write the POST/SOAP message in appropirate format(with the rigth XML format in the post body/soap message)!

Answer 1

Hello,
There's not one. The primary vision for the web-services.xml file
was/is to be a linkage between wsdl/soap and the j2ee environment. It
was not intended to be a starting point for building an application, but
a semi-private intermediary.
HTHs,
Bruce
Toni Nykanen wrote:
>
Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.