You can name it as some DAO as it is getting/sending data from/to a source, which is a web service in this case. I read some article and they have mentioned that a DAO is not necessarily used to get data from a traditional data source like Oracle DB. It can also interact with Db for information access.
I am working on an assignment (big smokes) which entails a similar concept, abstracting a web service behind a DAO is a good idea..because by definition a DAO is a data access object and data could be accessed from anywhere (Mainframe, Web Service, Database).
I have used this pattern in real life projects and it works really well...not when it comes to sun exam..not so sure
OCMJEA/SCEA, SCDJWS, SCBCD 1.3, SCJP 1.4
My SCEA experience:http://javalogue.blogspot.com/
Joined: Aug 03, 2010
As a second thought, considering performance reasons, I plan to consume/integrate web service in the presentation tier by using a POJO client class.
I think a adapter fits perfect.
You don't want to change your business logic or frontend, if the web-service interface changes in future...this way you provide
a interface that won't change, if the webservice may be replaced by another technology.