Win a copy of Head First Android this week in the Android forum!
  • 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 ...
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Al Hobbs
  • salvin francis

webservice client best practices

Ranch Hand
Posts: 125
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic