 |
 |
|
 |
 |
 |
 |
FYP Final Report v1.0.0
Copyright and All Rights Reserved To: Pee-Lo Team @2003/04
59
4.3.4.1 How Pee-LoMWA Consumes XML Web Services
Pee-LoMWA consumes XML web services similarly to that of Pee-LoWA. Therefore we will just
speed through this session with the simplest explanation possible. The codes should be familiar to
the readers by now.
Snippet 19: Sample Codes for Consuming Pee-LoWS XML Web Services by Pee-LoMWA
In Snippet 19, Line 48 and 49 declares objects for consuming data and invoking Pee-LoWS
respectively. Line 51 invokes the XML web service and the data it sends back is assigned to the
objPatient object. Line 53 and Line 54 is used for storing states of the client data at the
server since web access is a stateless environment. Codes from Line 55 to 63 will be to display
the data in objPatient onto the user UI.
Snippet 20: Sample Codes for Sending Data to Pee-LoWS XML Web Services by Pee-LoMWA
Snippet 20 on the other hand shows the codes that will send any user input data to Pee-LoWS. As
usual the code in Line 55 initialize an object; objCC as a container to store the user input data
before sending it over to Pee-LoWS and the code in Line 56 initialize an object; objWS to invoke
the remote web methods stored at Pee-LoWS. Codes from Line 58 to 64 will assign all user input
data to the objCC and Line 66 will invoke the Pee-LoWS remote web method that will actually
‘carry’ the data over the Internet to Pee-LoWS and have it committed to the database.
 |
|
 |
|