What are the unsolved / existing issues related with RESTful web services ?
What is the existing mechanism to identify the QOS level of the web service before its being consumed by a service consumer ?? Does the new UDDI version (3.0.2) support this ??
Is there any standard way to compose a RESTful web service ?
Can web service composition / Orchestration automated ?
Security is an issue. SOAP stacks have the full arsenal of tools afforded by WS-Security, but REST has only HTTP-based approaches (like Basic authentication and SSL encryption) available.
If by "compose" you mean "implement", then -in the Java world- there's the JAX-RS API and its reference implementation called Jersey. You might also look into WADL for describing such services, although not everybody agrees that it's useful or even desirable.
I wouldn't rely on UDDI to solve any WS-related problems. Just about nobody uses it.
So is there any standard way to compose web services dynamically without human interaction?
It means there's no standard way to identify the quality of a web service with out being consumed it ?
Is there any "Web service search engines" ?? How to publish a RESTful service in a service registry since there is no specific way to describe the service
Originally posted by upul indrajith:
Is there any standard way to compose a RESTful web service ??? Can web service composition / Orchestration automated ?
Indeed some have suggested that we are close to the end of code. That soon all the code will be generated instead of written. That programmers simply won't be needed because business people will generate programs from specifications.
Nonsense! We will never be rid of code, because code represents the details of the requirements. At some level these details cannot be ignored or abstracted; the have to be specified. And specifying requirements in such detail that a machine can execute them is programming. Such a specification is code.