This week's book giveaway is in the Android forum.
We're giving away four copies of Android Programming: The Big Nerd Ranch Guide and have Bill Phillips & Chris Stewart on-line!
See this thread for details.
Win a copy of Android Programming: The Big Nerd Ranch Guide this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

design for webservice publish  RSS feed

 
vasu chowdary
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a question like,for web application we mostly follow three layere architecture jsp --->web--->service---->dao---DB,which is the mostly used architecture for webservice publish?any one explain clearly?
 
Gabor Kovesdan
Greenhorn
Posts: 27
BSD Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
vasu chowdary wrote:I have a question like,for web application we mostly follow three layere architecture jsp --->web--->service---->dao---DB,which is the mostly used architecture for webservice publish?any one explain clearly?


I don't know if I totally understand what kind of answer you expect but I would say it depends on the development model. If you have Java first, I'd create a Fa├žade with a clear interface and coarse-grained methods and publish that as a Web Service endpoint. The rest of the system can be considered a black box. If you have WSDL first, then you generate the endpoint interface from WSDL. Then similarly, you implement the interface but how you do it internally is irrelevant. Use common best practices (layering, separation of concerns, proper encapsulation, etc.). If you have the meet-in-the-middle approach, then you will have a Java interface for your subsystem and an endpoint interface generated from WSDL. Use the GoF Adapter pattern to expose the subsystem with the proper interface.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!