• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Liutauras Vilda
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Saloon Keepers:
  • Scott Selikoff
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
  • Frits Walraven
Bartenders:
  • Stephan van Hulst
  • Carey Brown

Readonly Web services

 
Greenhorn
Posts: 4
Python C++ Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Guys,

What is the technology which I can accomplish such feature, have a readonly webservice? JAXWS or JAXRS(RESTfull)?

I'm working on TeamDoctor assignment and I have a requirement to to just read from web services and I don't know how to design such solution, any idea?

Thank you!
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A WS is an API that works over HTTP - if you don't want the API to be able to change anything, then don't provide methods that do that.
 
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The choice between SOAP WS and RESTful WS depends on how strongly you want the contract between the consumer and producer to defined.

If your WS is intented for B2B exchanges and can be used potentially by other external companies I would go for SOAP which strongly
defined the contract via WSDL.
If your WS is intented for internal use only in your company and the interface is simple enough like in your case, there is no
need for the SOAP overhead and I would go for RESTful WS.

I discarded here the social type of B2B integration where for example the MSN website calls the Facebook RESTful API to display
you facebook status in MSN. That's a particular case.
 
ntumba lobo
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have just downloaded 10 min ago my assignment and it is teamdoctor as well !
I guess I'll be facing the same design issue as you
 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This might help:

http://www.ajaxonomy.com/2008/xml/web-services-part-1-soap-vs-rest

esp. see pros/cons part.
 
The first person to drink cow's milk. That started off as a dare from this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic