From 8dfeb4e77e2a49e5a126203f32ecb4d06c8f45ec Mon Sep 17 00:00:00 2001 From: Frederic Peters Date: Thu, 25 Aug 2005 09:41:45 +0000 Subject: continuing on disco example, use the service to retrieve principal name. --- docs/reference/tmpl/data_service.sgml | 33 +++++++++++++++++++++++++++++---- 1 file changed, 29 insertions(+), 4 deletions(-) (limited to 'docs/reference') diff --git a/docs/reference/tmpl/data_service.sgml b/docs/reference/tmpl/data_service.sgml index c2c49469..8c70d473 100644 --- a/docs/reference/tmpl/data_service.sgml +++ b/docs/reference/tmpl/data_service.sgml @@ -6,9 +6,38 @@ ID-WSF Data Service Profile +XXX + + +Following up on #LassoDiscovery first example, it created a @service object, +this is a #LassoDataService instance. This example continues from that step +and retrieves the name of the principal: +msg_url + * the SOAP message is LASSO_WSF_PROFILE(service)->msg_body. The answer + * is stored in char* soap_answer; + */ + +lasso_data_service_process_query_response_msg(service, soap_answer); +principal_name = lasso_data_service_get_answer(service, "/pp:PP/pp:InformalName"); + +/* + * app should probably then use xmlNodeGetContent libxml2 function to get + * access to node content. + */ +]]> + @@ -22,10 +51,6 @@ ID-WSF Data Service Profile -@parent: -@resource_id: -@encrypted_resource_id: -@resource_data: -- cgit