Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • 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:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

SCDJWS-REST/SOAP Web services  RSS feed

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all

I'm preparing for web services exam. I have some doubts, I cant find correct explanation through website.
If anyone explains me it will really help for my exam. Thanks in Advance.

1) Is REST web service can be used for build a state full web services?

2) What is the difference between document and procedural web services?

3) How we can identify statefull and stateless web service?

4) Can we implement Statefull web service in EJB?

5)Can we maintain a state in EJB through web service?

6) How we can identify document or RPC based web service by seeing SOAP XML?

Even if you reply for one or two question...it will be fine...
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
1. If you create a stateful REST web service, I would say it is no longer a RESTful web service.
Statelessness is one of the core principles in the REST architectural style.
Reference: http://en.wikipedia.org/wiki/Representational_State_Transfer#Constraints

3. A stateful web service can retain some state specific to a particular client while a stateless web service seems to "see the client for the first time" with every request.
Stateful web services need to use some kind of mechanism to identify a particular client. This can be a token of some sort or HTTP cookies, provided that HTTP transport is used.

4. If I remember correctly, only stateless session beans can be exposed as web services.
This may have changed in JavaEE 6.
However, it is still possible to implement a stateful service based on stateless session beans, but you will probably have to write more code and use a token parameter to identify a specific client.

Best wishes!
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!