This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Web Services and the fly likes webservice client best practices Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "webservice client best practices" Watch "webservice client best practices" New topic

webservice client best practices

Mohit Sinha
Ranch Hand

Joined: Nov 29, 2004
Posts: 125
Hi there,

We are in the process of creating a web app which talks to a web service and not a database. I have experience building apps using the three tier (prezentation - service - dao) architecture always talking to the database.

I would want to know if I can stick to the same when the underlying system to communicate is a web service and not a database.
So accordingly I will have a controller layer which constructs the domain objects out of the form attributes and passes it on to the service layer. The service layer will do some biz stuff and then the DAO layer to access the web service.

With this background are there some already laid down best practices for developing web service (java) client apps.

The wsdl has around 15 odd operations.
Currently we have a service locator which gives us a ServiceInvocation object. We have to invoke methods on this ServiceInvocation to access different operations.

Do let me know your thoughts on the same.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
subject: webservice client best practices
Similar Threads
integration options for desktop applications
running java app as a batch job
exception handling approach for j2ee web apps
Unable to create JAXBContext - Don't know why
user authentication and dao