• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Rest Feature- No wsdl

 
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Friends,

I have following doubts in RESTfull web service. Please help me to clear on this.

1) To acces any service(Restfull) we can always use HTTP GET and get representaion of that resource. But I have a service which accepts some parameters and based on those it returns response.

Eg: To return a Employee details I need Passport number as a input from service provider.

In this case how service requestor knows what the input paraemeter. As we do not share any WSDL in Restfull, how service description is exposed?

2) I read one of the feature is REST is state less.....does it mean JAX-RPC/WS is state statefull. If yes please give me any example or link how it maintains state.

Thanks in advance.

Regards,
Sammeta phani
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
1. The only way clients of a RESTful web service can know about: At least an URI to start navigating from, the resource representation format, any additional parameters used in request URIs.
...is if the developer of the client learns about these things from some documentation.
Note that WSDL 2.0 and WADL support describing RESTful web services. I don't know to which extent they are used.
2. As far as I am concerned, SOAP web services should also be stateless.
It is possible to implement statefull web service using cookies, SOAP headers or some session identifier parameter, but I try to stay away from stateful services of any kind.
Best wishes!
 
sammeta Phanikumar
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

1) If we share the documentation...when ever functionality(reg input parameters) get changed then we have to share new documents. I think representing at URI is the bettter.

Thanks Ivan for your reply.

 
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sammeta,

Another one of these good IBM articles and this one is about Web services programming tips and tricks: Build stateful sessions in JAX-RPC applications which says -

An ongoing debate exists within the Web services community on whether the nature of Web services is stateless. While some developers propose specifications such as WS-Resource Framework to define stateful Web services, the JAX-RPC specification in wide use today primarily deals with the stateless services...



Regards,
Dan


 
sammeta Phanikumar
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Dan.


 
The longest recorded flight time of a chicken is 13 seconds. But that was done without this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic