Ulf Dittmer wrote:
M Rama wrote:I did look at WS-Security implementation in WebSphere and it does implement it. However, it doesn't seem to do the userid/password authentication but creates its own keys.
This sounds a bit odd. WS-Security is a standard - if WebSphere implements it, then it supports username/password authentication. Also, I don't understand what "it creates its own keys" means in the context of authentication.
Ulf Dittmer wrote:The Metro SOAP stack has an implementation of the WS-Security standard that allows you to do that. I'm not sure whether WebSphere (which I assume you're using) implements WS-Security, although I'd assume that it does - search its documentation for "WS-Security".
Hemanth H Bhat wrote:Well i don't think we would be able to create a full wsdl file based on a SOAP XML due to the following reasons
Its not necessary that the SOAP XML that you have would contain all the parameters that are supported by the wsdl as many optional parameters/Tags might be missing from the SOAP request or the SOAP response XML
Also the wsdl may support multiple web service operations so each operation will have a separate set of request and response SOAP XML's hence based on a single SOAP XML it would be hard to derive the complete wsdl file
James Ward wrote:Why not start with a Java Class, instead of SOAP.
Write a Java Class, with appropriate methods, and then use 'java2wsdl' command available in Axis2. You will find it in <AXIS2_HOME>\bin\ dir.
This is a good way to arrive at wsdl.