Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Web service
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Automated design methods{{anchor|Design methods}}=== [[File:SOA Detailed Diagram.png|thumb|right|upright=2|Web services in a [[service-oriented architecture]].]] Automated tools can aid in the creation of a Web service. For services using WSDL, it is possible to either automatically generate WSDL for existing classes (a bottom-up model) or to generate a class skeleton given existing WSDL (a top-down model). * A developer using a bottom-up model writes implementing classes first (in some programming language) and then uses a WSDL generating tool to expose methods from these classes as a Web service. This is simpler to develop but may be harder to maintain if the original classes are subject to frequent change.<ref>{{cite web |url=http://help.eclipse.org/kepler/index.jsp?topic=/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html |title=Creating bottom-up Web services |website=[[Eclipse (software)|Eclipse]] |access-date=11 November 2017}}</ref> * A developer using a top-down model writes the WSDL document first and then uses a code generating tool to produce the class skeleton, to be completed as necessary. This model is generally considered more difficult but can produce cleaner designs and is generally more resistant to change. As long as the message formats between the sender and receiver do not change, changes in the sender and receiver themselves do not affect the Web service. The technique is also referred to as ''contract first'' since the WSDL (or contract between sender and receiver) is the starting point.<ref>{{cite web |url=http://help.eclipse.org/kepler/index.jsp?topic=/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html |title=Creating top-down Web services |website = [[Eclipse (software)|Eclipse]] |access-date=11 November 2017}}</ref> * A developer using a Subset WSDL (SWSDL)<ref name=SWSDL>{{cite conference |doi=10.1109/CloudCom.2014.149 |conference=2014 IEEE 6th International Conference on Cloud Computing Technology and Science |title=Subset WSDL to Access Subset Service for Analysis |pages=688 |year=2014 |last=Chaturvedi |first=Animesh |isbn=978-1-4799-4093-6}}</ref> (i.e. a WSDL with the subset operation in the original WSDL) can perform Web service testing and top-down development.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Web service
(section)
Add topic