Microsoft Visual C++ .NET Professional Projects - Premier Press

710 Project 7

while(dataReader->Read())

{

i++;

}

dataReader->Close();

In the preceding code:

The set_CommandText method of the SqlCommand object is used to set

The Read method of the DataReader class moves to the next record.

Once the total number of the records is calculated, close the dataReader

All that remains to be done is to read from the database and fill the array with values. For accessing the content of each field from the DataReader object, you will use the get_Item method, which accepts either a string containing the name of the field or an integer that represents the index of the field:

dataReader=sCommand->ExecuteReader(); i=0;

while(dataReader->Read())

{

list1[i].ProdID=(dataReader->get_Item(“ProdID”))->ToString(); //Similarly for all the other fields

i++;

}

dataReader->Close(); return list1;

Once the array has been initialized, return the array to the calling application.

The following is the complete method:

Team-Fly®

CREATING A WEB SERVICE USING MANAGED EXTENSIONS Chapter 23 711

ArtArray Class1::getArtList()

{

int i=0;

SqlConnection *sConn=new SqlConnection();

sConn->set_ConnectionString(“Data Source=saik-d185;Initial

Catalog=ArtShop;Integrated Security=SSPI”);

sConn->Open();

SqlCommand *sCommand=new SqlCommand(NULL,sConn);

SqlDataReader *dataReader;

sCommand->set_CommandText(“select ProdID, ProdType, ProdName,ProdPrice,PictureFile from Product where ProdStatus=’unsold’”);

try{ dataReader=sCommand->ExecuteReader(); while(dataReader->Read())

{

i++;

}

dataReader->Close();

ArtArray list1=new ArtData __gc[i];

dataReader=sCommand->ExecuteReader(); i=0;

while(dataReader->Read())

{

list1[i].ProdID=(dataReader->get_Item(“ProdID”))->ToString(); list1[i].ProdType=(String *)dataReader->get_Item(“ProdType”); list1[i].ProdName=(String *)dataReader->get_Item(“ProdName”); list1[i].ProdPrice=(dataReader->get_Item(“ProdPrice”))->ToString(); list1[i].PictureFile=(String *)dataReader->get_Item(“PictureFile”); i++;

}

CREATING A WEB SERVICE USING MANAGED EXTENSIONS Chapter 23 713

int Class1::placeOrder(String *nProdID, String *nCustId,String *strDate)

{

String *strCmdTxt;

SqlConnection *sConn=new SqlConnection(); sConn->set_ConnectionString(“Data Source=Server1;Initial Catalog=ArtShop;Integrated Security=SSPI”); sConn->Open();

SqlCommand *sCommand=new SqlCommand(NULL,sConn);

SqlDataReader *dataReader;

Once you have connected to the database, create a command string to add a new record to the Orders table:

strCmdTxt=”insert into orders(ProdID,CustID,OrderDate) values(“; strCmdTxt=strCmdTxt->Concat(strCmdTxt,nProdID); strCmdTxt=strCmdTxt->Concat(strCmdTxt,”,”); strCmdTxt=strCmdTxt->Concat(strCmdTxt,nCustId); strCmdTxt=strCmdTxt->Concat(strCmdTxt,”,’”); strCmdTxt=strCmdTxt->Concat(strCmdTxt,strDate); strCmdTxt=strCmdTxt->Concat(strCmdTxt,”’)”); sCommand->set_CommandText(strCmdTxt);

try

{

dataReader=sCommand->ExecuteReader();

}

catch(Exception *e)

{

Console::WriteLine(e->Message); return 1;

}

return 0;

}

Once the Web service is built, it will be published to the ProdService virtual directory of your IIS installation.

CREATING A WEB SERVICE USING MANAGED EXTENSIONS Chapter 23 715

Here, you will build a Managed C++ client. You will add a list view to the client to display the items on sale at the art-shop.com site.

Next, right-click on the project name in the Solution Explorer window and select Add Web Reference. This will open the Add Web Reference dialog box, shown in Figure 23-7.

FIGURE 23-7 The Add Web Reference dialog box

This dialog box gives you the option of choosing a Web service from many locations:

Microsoft UDDI Directory. Allows you to select Web services from Microsoft’s production UDDI server.

Microsoft Test UDDI. Allows you to select Web services from Microsoft’s Test UDDI directory. This is used when you are developing Web service clients and want to use features like debugging.

Web reference on Local Web Server. Allows you to select Web services deployed on the local Web server installation.

In this project, you will select the Local Web Server option. Then, to the left of the dialog box, you see the root directory level DISCO XML document. At this point, you will take a small detour to see what this DISCO document is all about.

716 Project 7 CREATING WEB SERVICES

The process of investigating what Web services are available and how to use them is called Web service discovery, and DISCO files allow you to do it. DISCO files are actually XML Schemas that describe Web services. Visual Studio’s own version of the DISCO files are the VSDISCO files.

The default VSDISCO file is placed in the inetpub\wwwroot folder. It has the following structure:

<?xml version=”1.0” ?>

<dynamicDiscovery xmlns=”urn:schemas-dynamicdiscovery:disco.2000-03-17”>

<exclude path=”_vti_cnf” /> <exclude path=”_vti_pvt” /> <exclude path=”_vti_log” /> <exclude path=”_vti_script” /> <exclude path=”_vti_txt” />

</dynamicDiscovery>

The <exclude path=> tells the dynamic discovery process what folders to exclude from a search for Web services.

If you navigate to a VSDISCO file from a browser, a search is performed for all Web services in all the folders lying one level below the folder containing the VSDISCO file. The folders listed in the VSDISCO file are excluded from the search. An XML document containing information about all the Web services found is returned.

On the right of the Add Web Reference dialog box you will see a list of the available Web services, as shown in Figure 23-8.

Select the link for the ProdService Web service. This will display the VSDISCO file for the Web service, as shown in Figure 23-9. Also on the right side of the dialog box you will see two links:

View Contract. Displays the WSDL file for the Web service.

View Documentation. Displays a list of operations supported by the Web service. Here, you should see the description that you added to the

Description parameter of the WebMethod attribute. This helps a developer creating a client application to decide if a particular Web service has an operation that is required by a client application.

CREATING A WEB SERVICE USING MANAGED EXTENSIONS Chapter 23 717

FIGURE 23-8 Add Web Reference dialog box with a listing of available Web services

FIGURE 23-9 Add Web Reference dialog box with details of the selected Web services

Information about the operations supported by a Web service is obtained from the WSDL file. Take a quick look at the WSDL file:

<definitions xmlns:http=”http://schemas.xmlsoap.org/wsdl/http/”

xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”

CREATING A WEB SERVICE USING MANAGED EXTENSIONS Chapter 23 719

<part name=”Body” element=”s0:ArrayOfArtData” />

</message>

Each operation can be accessed using GET, POST, and SOAP methods. Each of these methods has a pair of In/Out messages. For example, in the preceding sam-

ple, getArtListHttpPostIn and getArtListHttpPostOut are the messages for

accessing the Web service using the HTTP POST method.

Next, you will take a look at the <port> elements:

<portType name=”Class1Soap”>

- <operation name=”getArtList”>

<documentation>This method returns a list of products available at artshop.com</documentation>

<input message=”s0:getArtListSoapIn” /> <output message=”s0:getArtListSoapOut” />

</operation>

</portType>

<port> types are a collection of a named set of operations. The port type also binds the collection of operations to the protocol used, such as HTTP POST and HTTP GET. The Operations node lists one or more methods that a Web service will expose.

The last element that you need to be aware of is the <binding> element:

<binding name=”Class1HttpGet” type=”s0:Class1HttpGet”> <http:binding verb=”GET” />

- <operation name=”getArtList”> <http:operation location=”/getArtList” />

- <input> <http:urlEncoded />

</input>

- <output>

<mime:mimeXml part=”Body” /> </output>

</operation>

</binding>