Sekar,
I believe you are right. In my view the WSDL and UDDI concept is if you want to distribute your services to the world. For an internal app (service) I don't see the need for the WSDL and UDDI. Right now I am working on using WSDL to generate a SOAP request and call a service. I have an implementation where a servlet does this. I am trying to see the need to use the WSDL w/n an internal app when you know your services. One benefit of WSDL, you don't need to write code to generate your SOAP request, just load a WSDL and have it dynamically generate your soap request? If I am in error in my assumptions please correct me.
Regards
Richard
[EMAIL PROTECTED] wrote:
Hello,
Is SOAP could be used in an application for just exchanging data across the
wire, without using the WSDL and UDDI concept.
Imagine , I do not need a web service concept, but my application need to
transfer XML data across the wire to another applications.
Does it make sense to use SOAP only to wrap XML message.
Thanks,
Sekar.
------------------------------
email - [EMAIL PROTECTED]
Home - 972.869.9878
Cell - 972.567.7536
------------------------------
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 a year!
http://personal.mail.yahoo.com/
