aspose file tools*
The moose likes Web Services and the fly likes webservice design pattern Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "webservice design pattern " Watch "webservice design pattern " New topic
Author

webservice design pattern

Laxman Nagalla
Greenhorn

Joined: Feb 01, 2008
Posts: 10
Hi All,

I need to understand which one is the best design pattern for my requirement.

We are the servers needs to provide the web service to clients. Clients send the request with the request we need to search the field in our database and send the multiple values as response.

Suggest which design pattern fit.


Thanks & Regards<br />Laxman N
Vijitha Kumara
Bartender

Joined: Mar 24, 2008
Posts: 3775

It looks bit vague when you say like that. What options have you looked at here? You can send a SOAP response or similar in this case? What particular issues you have faced?


SCJP 5 | SCWCD 5
[How to ask questions] [Twitter]
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12671
    
    5
We are the servers needs to provide the web service to clients. Clients send the request with the request we need to search the field in our database and send the multiple values as response.


You need to flesh out your requirements before starting to think about abstractions like design patterns.

The first question that occurs to me is what are your clients expecting?

The big choice for a web service is SOAP versus RESTful architecture. Are your clients committed to one or the other?

Are they accessing your service by web browser or custom client software?

Do clients ever update your database with new data or are all transaction read only?

Bill

Java Resources at www.wbrogden.com
Laxman Nagalla
Greenhorn

Joined: Feb 01, 2008
Posts: 10
Thanks William for your response.

Below is my answer for your questions.

The first question that occurs to me is what are your clients expecting?

Response: Clients expects is they will send the request of one field we need to search the field in our DB and send the response back with few fields in that record.

The big choice for a web service is SOAP versus RESTful architecture. Are your clients committed to one or the other?
Response: No one is committed for any web service. We thought we can implement in SOAP service.

Are they accessing your service by web browser or custom client software?
Response: through web browser

Do clients ever update your database with new data or are all transaction read only?

Response: All the transaction are read only.
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12671
    
    5
This is very clearly suitable for a RESTful architecture service. With utterly no reason to consider SOAP.

REST is an "architecture" ie a Design Pattern controlled by a fixed meaning for the HTTP methods - in your case all user requests are GET - which implies returning the present state of a resource. A traditional web service in other words.

Bill

 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: webservice design pattern
 
Similar Threads
Need of Model in mvc
Design pattern and mutlthreading
Design question
Intercepting filter pattern vs Front Controller
How to differentiate between a normal get post handling and rest architecture