Nishant, I am not saying CAS couldn't be made to include a SOAP interface, however SOAP is more than HTTP. CAS would need to include some type of XSD for CAS1 & CAS2 protocol, server side logic to handle SOAP requests, and maybe some client side support to generate SOAP requests. However, no one has really requested such a feature as the RESTful API and normal client support has met most use cases.
Why are you trying to use a SOAP interface rather than interactive usage or RESTful API? A- On 7/27/09 8:58 AM, "Nishant" <[email protected]> wrote: > Hi, > > SOAP is based on HTTP Protocol. > So, why can't we use that? -- Andrew Feller, Business System Programmer LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
