[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrf] Interop suggestions
Hi Rick, Thanks for these suggestions. 1) +1 - That's a good idea: having a fresh printer would avoid any mess left over by a previous test. I propose adding a new portType to the existing WSDL. 2) +1 - My mistake. Also, there is a response to Send_Document and it will be clearer if it is documented in the same way as the other exchanges. We haven't discussed (among the TC/interop participants ) a process for updating the Interop scenarios. Shall we do it via the Issues list? One constraint I can see is that Interop issues may need to be dealt with quickly. Regards, Tim Banks rineholt@us.ibm.com wrote on 17/01/2005 16:41:23: > I'd like to propose the following changes to the WSRF Interop: > > 1) Provide a standard means for each participant to obtain a unique > "fresh" printer resource to test against > Each participant provide a URL to a printer factory type web > service with the following request/response format > > request: > <SOAP-ENV:Body> > <wsrf-pr:createPrinter/> > </SOAP-ENV:Body> > > reply: > <SOAP-ENV:Body> > <wsrf-pr:createPrinterResponse> > <wsrf-pr:printerEPR> > <!-- epr content goes here --> > </wsrf-pr:printerEPR> > </wsrf-pr:createPrinterResponse> > </SOAP-ENV:Body> > > 2) The non WSRF operations follow the wsrf pattern of a single > document in the SOAP body > Specifically, section 3.1 Print_Job, request and response as a > suggestion: > <SOAP-ENV:Body> > <wsrf-pr:Print_Job> > <wsrf-pr:job_name>My First Printer Job</wsrf-pr:job_name> > <wsrf-pr:document_format>text/plain</wsrf-pr:document_format> > <wsrf-pr:Base64Data>SGVsbG8gV29ybGQh</wsrf-pr:Base64Data> > </wsrf-pr:Print_Job> > </SOAP-ENV:Body> > > <SOAP-ENV:Body> > <wsrf-pr:Print_JobResponse> > <wsrf-pr:SuccessStatusCode>successful-ok</wsrf-pr:SuccessStatusCode> > <wsrf-pr:job_reference> > <wsa:Address> > http://www.WSRF-Examples.org/IPPprinters/Jobs > </wsa:Address> > <wsa:ReferenceProperties> > <job_id>1</job_id> > </wsa:ReferenceProperties> > <wsa:PortType>wsrf-prw:Job</wsa:PortType> > </wsrf-pr:job_reference> > <wsrf-pr:job_state>pending</wsrf-pr:job_state> > </wsrf-pr:Print_JobResponse> > </SOAP-ENV:Body> > > ... and Same for Send_Document > <SOAP-ENV:Body> > <wsrf-pr:Send_Document> > <wsrf-pr:last_document>true</wsrf-pr:last_document> > <wsrf-pr:document_format>text/plain</wsrf-pr:document_format> > <wsrf-pr:Base64Data> > Q29uZ3JhdHVsYXRpb25zLCB5b3UndmUgcmVh > Y2hlZCB0aGUgZW5kIG9mIHRoZSBTY2VuYXJpbyE= > </wsrf-pr:Base64Data> > </wsrf-pr:Send_Document> > </SOAP-ENV:Body> > > Should we have the response for Send_Document ? Or should it be oneway?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]