The next logical step is to implement multiple interfaces on the same Web
service. You do this by applying multiple
WebServiceBinding
attributes
to the class implementing the Web service. On each Web method you set the
SoapDocumentService
or
SoapRpcService
Binding
property to the name of the binding that contains this method. Taking the
SupplierIface1
class in Listing 8.1, you might want to factor out its
methods into two interfaces:
IOrderMgmt
and
IQuoteMgmt
.
Listing 8.6 shows the code used to achieve this.
<WebServiceBinding( _
Name:="IOrderMgmt", _
[Namespace]:="http://LearnXmlWS.com/Supplier"), _
WebServiceBinding( _
Name:="IQuoteMgmt", _
[Namespace]:="http://LearnXmlWS.com/Supplier"), _
WebService([Namespace]:="http://LearnXmlWS.com/Supplier")> _
Public Class SupplierIface2
Inherits System.Web.Services.WebService
<WebMethod( _
Description:= _
"Places the order then returns the new order id"), _
SoapDocumentMethod(Binding:="IOrderMgmt")> _
Public Function PlaceOrder( _
ByVal newOrder As Order) As String
'returns a new order id
End Function
<WebMethod(), _
SoapDocumentMethod(Binding:="IOrderMgmt")> _
Public Function CheckStatus( _
ByVal OrderId As String) As OrderInfo
'returns an orderinfo structure
End Function
<WebMethod(), _
SoapDocumentMethod(Binding:="IQuoteMgmt")> _
Public Function GetPriceQuote( _
ByVal newOrder As Order) As QuoteInfo()
'returns an orderinfo structure
End Function
End Class
Note that there are two bindings with different namesboth in the same
namespace. Also,
GetPriceQuote
is now part of the
IQuoteMgmt
binding.
Listing 8.7 shows the bindings defined in the resulting WSDL document.
Listing 8.7 The resulting WSDL document with two bindings
(VBWSBook\Chapter8\MultiInterface.wsdl)
To implement these interfaces you run wsdl.exe with the /server parameter
just as you did for the single interface case. However, the output this time is
different: You get one file that contains two classesone for each binding.
The first class you get,
IQuoteMgmt
, has one method called
GetPriceQuote
. The second class,
IOrderMgmt
, has two methods
called
PlaceOrder
and
CheckStatus
. You can add this file to
your Web service project and create classes that inherit from each of
IQuoteMgmt
and
IOrderMgmt,
and then start implementing each
interface's methods. For example, Listing 8.8 shows a Web service that
implements IQuoteMgmt.
Listing 8.8 An example Web service that implements IQuoteMgmt
(VBWSBook\Chapter8\InterfaceImpl\QuoteMgmtImpl.asmx.vb)
Imports System.Web.Services
Imports System.Web.Services.Protocols
<WebServiceBinding( _
Name:="IQuoteMgmt", _
Namespace:="http://LearnXmlWS.com/Supplier", _
Location:= _
"http://vbwsserver/vbwsbook/chapter8/MultiInterface.wsdl"), _
WebService(Namespace:="http://tempuri.org/")> _
Public Class QuoteMgmtImpl
Inherits MultiIface1.IQuoteMgmt
<WebMethodAttribute(), _
SoapDocumentMethodAttribute( _
"http://LearnXmlWS.com/Supplier/GetPriceQuote", _
RequestNamespace:="http://LearnXmlWS.com/Supplier", _
ResponseNamespace:="http://LearnXmlWS.com/Supplier", _
Use:=Description.SoapBindingUse.Literal, _
ParameterStyle:=SoapParameterStyle.Wrapped, _
Binding:="IQuoteMgmt")> _
Public Overrides Function GetPriceQuote( _
ByVal newOrder As InterfaceImpl.MultiIface1.Order) _
As InterfaceImpl.MultiIface1.QuoteInfo()
End Function
End Class
Since .NET supports single inheritance, a class cannot inherit from more than
one base class. This means you cannot create a Web service that inherits from
both classes generated by wsdl.exe (the classes IQuoteMgmt and IOrderMgmt). You
will end up with a Web service class for each binding you want to implement.
This is not exactly what comes to mind when I think of multiple interfaces.
Ideally, we can have one Web service class that implements both IQuoteMgmt and
IOrderMgt. While it's possible to achieve this, you can't do it by
inheriting from abstract classes generated by wsdl.exe. Instead, you must create
a Web service class, and then manually specify the bindings and the methods. The
process is almost identical to the single-interface implementation case except
you are not overriding any base class methods. The steps for implementing
multiple interfaces on a single Web service class are:
Create a Web service.
Add a WebServiceBinding attribute to the Web service class for each
interface you want to implement. Specify the binding's name, namespace, and
location (the URL of a WSDL document where the binding is defined).
Create WebMethods on this Web service that correspond to the operations
defined in each binding. You can get some help from wsdl.exe by running it with
the /server flag then copying the abstract method definitions it creates and
pasting them into your Web service. If you do this, be sure to remove the
MustOverride keyword from those methods.
Specify the binding name for each Web method. This name must match one of
the binding names defined by SoapServiceBinding attributes on the Web service
class.
Listing 8.9 shows an example Web service class that implements both
IQuoteMgmt and IOrderMgmt.
Listing 8.9 A single Web service class that implements both IQuoteMgmt and
IOrderMgmt interfaces (VBWSBook\Chapter8\InterfaceImplMultipleInterfaceImpl.asmx.vb)
Imports System.Web.Services
Imports System.Web.Services.Protocols
<WebService(Namespace:="http://tempuri.org/"), _
WebServiceBindingAttribute(Name:="IQuoteMgmt", _
[Namespace]:="http://LearnXmlWS.com/Supplier", _
Location:= _
"http://vbwsserver/vbwsbook/chapter8/MultiInterface.wsdl"), _
WebServiceBindingAttribute(Name:="IOrderMgmt", _
[Namespace]:="http://LearnXmlWS.com/Supplier", _
Location:= _
"http://vbwsserver/vbwsbook/chapter8/MultiInterface.wsdl")> _
Public Class MultipleInterfaceImpl
Inherits WebService
<WebMethodAttribute(), _
SoapDocumentMethodAttribute( _
"http://LearnXmlWS.com/Supplier/GetPriceQuote", _
RequestNamespace:="http://LearnXmlWS.com/Supplier", _
ResponseNamespace:="http://LearnXmlWS.com/Supplier", _
Use:=Description.SoapBindingUse.Literal, _
ParameterStyle:=SoapParameterStyle.Wrapped, _
Binding:="IQuoteMgmt")> _
Public Function GetPriceQuote( _
ByVal newOrder _
As InterfaceImpl.MultiIface1.Order) _
As InterfaceImpl.MultiIface1.QuoteInfo()
End Function
<WebMethodAttribute(), _
SoapDocumentMethodAttribute( _
"http://LearnXmlWS.com/Supplier/PlaceOrder", _
RequestNamespace:="http://LearnXmlWS.com/Supplier", _
ResponseNamespace:="http://LearnXmlWS.com/Supplier", _
Use:=Description.SoapBindingUse.Literal, _
ParameterStyle:=SoapParameterStyle.Wrapped, _
Binding:="IOrderMgmt")> _
Public Function PlaceOrder( _
ByVal newOrder As InterfaceImpl.MultiIface1.Order) _
As String
End Function
<WebMethodAttribute(), _
SoapDocumentMethodAttribute( _
"http://LearnXmlWS.com/Supplier/CheckStatus", _
RequestNamespace:="http://LearnXmlWS.com/Supplier", _
ResponseNamespace:="http://LearnXmlWS.com/Supplier", _
Use:=Description.SoapBindingUse.Literal, _
ParameterStyle:=SoapParameterStyle.Wrapped, _
Binding:="IOrderMgmt")> _
Public Function CheckStatus(ByVal OrderId As String) _
As InterfaceImpl.MultiIface1.OrderInfo
End Function
End Class
The Web service class in Listing 8.9 has two WebServiceBinding attributes for
IQuoteMgmt and ISupplierMgmt. Inside the class, you'll see the
GetPriceQuote Web method that belongs to the IQuoteMgmt interface. You'll
also see the IOrderMgmt interface methods: PlaceOrder and CheckStatus. Listing
8.10 shows the resulting WSDL.
Listing 8.10 The WSDL for the service in Listing 8.9
The most interesting feature of the WSDL in Listing 8.10 is the presence of
two
<port>
elements inside the
<service>
element,
indicating that the service implements two different interfaces.
Overview
Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.
This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.
Collection and Use of Information
To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:
Questions and Inquiries
For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.
Online Store
For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.
Surveys
Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.
Contests and Drawings
Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.
Newsletters
If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply
email
[email protected]
.
Service Announcements
On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.
Customer Service
We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our
Contact Us form
.
Other Collection and Use of Information
Application and System Logs
Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.
Web Analytics
Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.
Cookies and Related Technologies
This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.
Do Not Track
This site currently does not respond to Do Not Track signals.
Security
Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.
Children
This site is not directed to children under the age of 13.
Marketing
Pearson may send or direct marketing communications to users, provided that
Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.
Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.
Correcting/Updating Personal Information
If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the
Account page
. If a user no longer desires our service and desires to delete his or her account, please contact us at
[email protected]
and we will process the deletion of a user's account.
Choice/Opt-out
Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive:
www.informit.com/u.aspx
.
Sale of Personal Information
Pearson does not rent or sell personal information in exchange for any payment of money.
While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to
[email protected]
.
Supplemental Privacy Statement for California Residents
Pearson may disclose personal information, as follows:
As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.
Links
This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.
Requests and Contact
Please
contact us
about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.
Changes to this Privacy Notice
We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.