sathya sai schrieb:
>
> Hi Elmar,
>
> Although we had defined "wprt" as a namespace prefix for
>
http://schemas.microsoft.com/windows/2006/08/wdp/print URL in our
> gSoap file, the ws4d-gSoap tool seems to be somehow ignoring "wprt"
> prefix and then adds "n1" to it. The same behavior could be observed
> with the sample Airconditioner application as well.
>
> However, I could fix this problem by explicitly adding "wprt" prefix in
> acs_setup_HostingService() function as in below,
>
> ----
> device_type = ws4d_qname_alloc (1, &device->alloc_list);
> *device_type->prefix = ws4d_strdup (**"wprt"**, &device->alloc_list);*
> device_type->ns = ws4d_strdup
> (
http://schemas.microsoft.com/windows/2006/08/wdp/print,
> &device->alloc_list);
> device_type->name = ws4d_strdup ("PrintDeviceType", &device->alloc_list);
>
OK, this code should be generated by ws4d-gsoap code generator if you
define the
http://schemas.microsoft.com/windows/2006/08/wdp/print namespaces with the prefix wprt and add the fixedprefixes="wprt" in the
metadata.xml file.
> ---
>
> Now the problem is, although our WSD server is sending the ProbeMatch
> response with "
> wprt:PrintDeviceType wsdp:Device", vista client is dropping after
> receiving ResolveMatch match (same old behavior.)
>
> I just compared the XML packet exchange between vista
client &
> someother WSD supported printer & see that although the ProbeMatch
> packet is similar to us but ResolveMatch packet seems be different.
>
> ResolveMatch response of someother WSD server which is working:
> =================================================
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
> xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> xmlns:wse="
http://schemas.xmlsoap..org/ws/2004/08/eventing"
> xmlns:xop="
http://www.w3.org/2004/08/xop/include"
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> xmlns:wscn="
http://schemas.microsoft.com/windows/2006/08/wdp/scan"
> xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> xmlns:xrxd="
http://xml.namespaces.xerox.com/enterprise/wsd/discovery/2007/02"
> xmlns:trn="
http://schemas.xmlsoap.org/ws/2004/09/transfer"
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print">
> <SOAP-ENV:Header>
> <wsa:Action>
http://schemas.xmlsoap.org/ws/2005/04/discovery/ResolveMatches</wsa:Action>
> <wsa:MessageID>urn:uuid:6f030bb8-2f8d-11de-aebe-0000aa9e8e1a</wsa:MessageID>
> <wsa:RelatesTo>urn:uuid:f2567a08-aead-42cc-b308-10a3b4f4f227</wsa:RelatesTo>
> <wsa:To>
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> <wsd:AppSequence MessageNumber="12"
>
InstanceId="1240438886"></wsd:AppSequence>
> </SOAP-ENV:Header>
> <SOAP-ENV:Body>
> <wsd:ResolveMatches>
> <wsd:ResolveMatch>
> <wsa:EndpointReference>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> </wsa:EndpointReference>
> *<**wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types**>*
> *<**wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs**>*
> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> </wsd:ResolveMatch>
> </wsd:ResolveMatches>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> ResolveMatch response of WSD server created by our ws4d-gSoap stack
> which is not
working:
> =====================================================
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
> xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
> xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print"
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof">
> <SOAP-ENV:Header>
> <wsa:MessageID
> SOAP-ENV:mustUnderstand="true">urn:uuid:ac2f7378-d30d-453b-8d6c-babe2c625b5f</wsa:MessageID>
> <wsa:RelatesTo
> SOAP-ENV:mustUnderstand="true">urn:uuid:b9a0faf1-0ad5-4b5c-8e20-9b39d548c324</wsa:RelatesTo>
> <wsa:To
> SOAP-ENV:mustUnderstand="true">urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To>
> <wsa:Action
> SOAP-ENV:mustUnderstand="true">
http://schemas.xmlsoap.org/ws/2005/04/discovery/ResolveMatches</wsa:Action>
> <wsd:AppSequence MessageNumber="9" InstanceId="1031797"></wsd:AppSequence>
> </SOAP-ENV:Header>
> <SOAP-ENV:Body>
> <wsd:ResolveMatches>
> <wsd:ResolveMatch>
> <wsa:EndpointReference>
> <wsa:Address>urn:uuid:a2bb3689-62ff-4d13-8da8-82171e0916c3</wsa:Address>
> </wsa:EndpointReference>
> *<**wsd:XAddrs>
http://10.208.24.167:1306</wsd:XAddrs**>*
> <wsd:MetadataVersion>1031797</wsd:MetadataVersion>
> </wsd:ResolveMatch>
> </wsd:ResolveMatches>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> I could observe following two differences,
>
> 1. Our
ResolveMatch packet didn't contain "*<wsd:Types>wsdp:Device
> wprt:PrintDeviceType</wsd:Types>" *field in it.
>
This should be OK, the Types field is optional.
>
> 2. Our ResolveMatch packet had
> *"<wsd:XAddrs>
http://10.208.24.167:1306</wsd:XAddrs**>" *but the the
> working WSD server seems to be sending
> *<**wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs**>"*
>
This should also be OK, as there are no restrictions on service uri.
> **
> Could you please let me know with your thoughts by earliest to proceed
> further on this.
>
Are you sure, that Vista does drop the Resolve Matches? Can you look, if
there is a WS-Transfer
get request to
http://10.208.24.167:1306 ? I
think that Vista will drop the WS-Transfer get response as you have to
add the pnp-x things.
If you compile ws4d-gsoap and your device in debug mode, which is the
default, you can look at the message log. The log files are created in
the working directory, where you are running the device. RECV.log is for
incomming messages and SENT.log is for outgoing messages. You can look
for the WS-Transfer messages there.
I'm not in my office this week, so I don't have internet all the time,
but i will have internet in the evening and try to answer your mails as
soon as possible.
Regards,
Elmar Zeeb
>
> Thanks a lot in advance.
>
> Regards,
> Sathya
>
>
>
> --- On *Fri, 4/24/09, Elmar Zeeb /<
elmar.zeeb@uni-rostock..de>/* wrote:
>
>
> From: Elmar Zeeb <
elmar..zeeb@uni-rostock.de>
> Subject: Re: Regarding WS-Policy support on wsdl2h.exe
> To:
ws4d-gs...@googlegroups.com> Date: Friday, April 24, 2009, 7:19 PM
>
>
> OK, then you have to check if you have defined the wprt prefix for
> the
> printer device namespace in the gsoap file. There should be a line
>
saying:
>
> //gsoap wprt schema namespace:
>
http://schemas.microsoft.com/windows/2006/08/wdp/print>
> If there is something other than wprt, then you have to change the
> prefix to wprt and search for the old prefix in the file and
> replace it
> with wprt everywhere.
>
> sathya sai schrieb:
> > I had added the following change onto metadata.xml (missed to
> send in
> > my previous mail)
> >
> > <wdp:Relationship
>
> Type="
http://schemas.xmlsoap.org/ws/2006/02/devprof/host">
> > <wdp:Host fixedprefixes="wprt">
> > <wdp:Types>wprt:Printer</wdp:Types>
> > <wdp:ServiceId>DPWS-HostingService</wdp:ServiceId>
> > </wdp:Host>
> > <wdp:Hosted fixedprefixes="wprt">
> > <wdp:Types>wprt:PrinterServiceType</wdp:Types>
> > <wdp:ServiceId>
http://WsdServiceId/1> <
http://wsdserviceid/1></wdp:ServiceId>
> > <Name>PrinterService</Name>
> > <Extension>
> > <pnpx:CompatibleId
> >
> xmlns:pnpx=\"
http://schemas..microsoft.com/windows/pnpx/2005/10\">
http://schemas.microsoft.com/windows/2006/08/wdp/print/PrinterServiceType</pnpx:CompatibleId>
> <
http://schemas.microsoft.com/windows/pnpx/2005/10/%22%3Ehttp://schemas.microsoft.com/windows/2006/08/wdp/print/PrinterServiceType%3C/pnpx:CompatibleId%3E>
> > </Extension>
> > </wdp:Hosted>
> > </wdp:Relationship>
> >
> >
> > --- On *Fri, 4/24/09, sathya sai /<
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>/*
> wrote:
> >
>
>
> > From: sathya sai <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> > Subject: Re: Regarding WS-Policy support on wsdl2h.exe
> > To: "Elmar Zeeb" <
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo..com/mc/compose?to=elmar...@uni-rostock.de>>
> > Cc:
ws4d-gs...@googlegroups.com> <
http://us.mc954.mail.yahoo.com/mc/compose?to=ws4d-gs...@googlegroups.com>,
> "sathya" <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_eshwar@yahoo.co..in>>
>
> Date: Friday, April 24, 2009, 6:08 PM
> >
> >
> > Hi Elmar,
> >
> > Even after adding the following as suggested by you onto
> > metadata.xml, still the ProbeMatch seems to have "n1" prefix &
> > thus causing old behavior to still prevail. Please find
> below the
> > corresponding ProbeMatch response packet from the WSD server,
> >
> >
---
> > <?xml version="1.0" encoding="UTF-8"?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
> > xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> > xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
> > xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> > xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> > xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> >
> xmlns:n1="
http://schemas.microsoft.com/windows/2006/08/wdp/print">
> >
.<SOAP-ENV:Header>
> > ..<wsa:MessageID
> >
> SOAP-ENV:mustUnderstand="true">urn:uuid:b78a2d7a-c3bd-4b37-8714-256484850e35</wsa:MessageID>
> > ..<wsa:RelatesTo
> >
> SOAP-ENV:mustUnderstand="true">urn:uuid:0416b2a3-3279-4544-9a55-3809c3d74999</wsa:RelatesTo>
> > ...<wsa:To
> >
> SOAP-ENV:mustUnderstand="true">
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> >
..<wsa:Action
> >
> SOAP-ENV:mustUnderstand="true">
http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action>
> > ..<wsd:AppSequence MessageNumber="4"
> > InstanceId="807026"></wsd:AppSequence>
> > .</SOAP-ENV:Header>
> > .<SOAP-ENV:Body>
> > ..<wsd:ProbeMatches>
> > ...<wsd:ProbeMatch>
> >
....<wsa:EndpointReference>
> >
> .....<wsa:Address>urn:uuid:a2bb3689-62ff-4d13-8da8-82171e0916c3</wsa:Address>
> > ......</wsa:EndpointReference>
> > ......<wsd:Types>n1:Printer wsdp:Device</wsd:Types>
> > ....<wsd:Scopes></wsd:Scopes>
> > .....<wsd:MetadataVersion>807210</wsd:MetadataVersion>
> > ...</wsd:ProbeMatch>
> > ..</wsd:ProbeMatches>
> > .</SOAP-ENV:Body>
>
> </SOAP-ENV:Envelope>
> > ---
> >
> > Could you please let me know your thoughts on this.
> >
> > Thanks and regards,
> > Sathya
> >
> > --- On *Fri, 4/24/09, Elmar Zeeb
> /<
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>/*
> wrote:
> >
> >
> > From: Elmar Zeeb <
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>
> > Subject: Re: Regarding WS-Policy support on wsdl2h.exe
> > To: "sathya sai" <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> > Date: Friday, April 24, 2009, 4:09 PM
> >
> > sathya sai schrieb:
> >>
> >> Hi Elmar,
> >>
> >> Thanks a lot for your continuous support
towards me..
> >>
> >> Hope you are busy & you couldn't get a chance to have a
> look
> >> at my previous mail
> >>
> > To be onest, i read your mail but didn't really
> understand it.
> > But now i see what you are doing...
> >>
> >> To add-on to this, I could see that Microsoft vista's WSD
> >>
server sends the following ProbeMatch & ResolveMatch packet
> >> which differs from us which could be causing the
> problem. The
> >> problem I am facing now is, when I do a search of WSD
> servers
> >> from vista client, vista client somehow drops the packet
> >> after ResolveMatch and doesn't issue Get metadata after
> that.
> >>
> > I know this problem. The printerdevice specification
> specifies
>
> static namespace prefixes. This is quite uncommon, but
> > microsoft can do this :-)
> >>
> >> Vista WSD server's
> >> ----------------------------
> >>
> >> <wsd:ProbeMatches>
> >> <wsd:ProbeMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> >> </wsa:EndpointReference>
> >> <wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types>
> >>
> <wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs>
> >> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> >> </wsd:ProbeMatch>
>
>> </wsd:ProbeMatches>
> >>
> >> ...
> >>
> >> <wsd:ResolveMatches>
> >> <wsd:ResolveMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> >> </wsa:EndpointReference>
>
>> <wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types>
> >>
> > this device uses the wprt prefix for the printerdevice
> > namespace. This is correct.
> >>
> <wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs>
> >> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> >> </wsd:ResolveMatch>
>
>> </wsd:ResolveMatches>
> >>
> >> Our WSD server (created using ws4d-gSoap stack),
> >>
> >> <wsd:ProbeMatches>
> >> <wsd:ProbeMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>urn:uuid:a2bb3689-62ff-4d13-8da8-82171e0916c3</wsa:Address>
> >>
</wsa:EndpointReference>
> >> <wsd:Types>n1:PrintDeviceType wsdp:Device</wsd:Types>
> >>
> > this ws4d-gsoap based device uses the n1 prefix for the
> > printerdevice namespace. In this case that is not correct.
> >> <wsd:Scopes></wsd:Scopes>
> >> <wsd:MetadataVersion>798243</wsd:MetadataVersion>
> >> </wsd:ProbeMatch>
> >>
</wsd:ProbeMatches>
> >>
> >>
> >> <wsd:ResolveMatches>
> >> <wsd:ResolveMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>urn:uuid:a2bb3689-62ff-4d13-8da8-82171e0916c3</wsa:Address>
> >> </wsa:EndpointReference>
> >> <wsd:XAddrs>
http://10.208..24..167:2463> <
http://10..208..24.167:2463/></wsd:XAddrs>
> >> <wsd:MetadataVersion>798243</wsd:MetadataVersion>
> >> </wsd:ResolveMatch>
> >> </wsd:ResolveMatches>
> >>
> >> -----------
> >>
> >> Could you please help me out with out thoughts to
further
> >> proceed on this... A quick doubt, have we tested the
> >> compatiblity with vista clients earlier.
> >>
> > You can change this by specifying a custom prefix in the
> > device metadata (metadata.xml)
> >
> > There should be something like this in the section where the
> > device is defined:
> > <wdp:Relationship
> >
Type="
http://schemas.xmlsoap.org/ws/2006/02/devprof/host">
> > <wdp:Host fixedprefixes="wprt">
> > <wdp:Types>wprt:Printer</wdp:Types>
> > <wdp:ServiceId>DPWS-HostingService</wdp:ServiceId>
> > </wdp:Host>
> > <wdp:Hosted fixedprefixes="wprt">
> >
<wdp:Types>wprt:PrinterServiceType</wdp:Types>
> > <wdp:ServiceId>
http://WsdServiceId/1> <
http://wsdserviceid/1></wdp:ServiceId>
> > <Name>PrinterService</Name>
> > <Extension><pnpx:CompatibleId
> >
> xmlns:pnpx=\"
http://schemas.microsoft.com/windows/pnpx/2005/10\">
http://schemas.microsoft.com/windows/2006/08/wdp/print/PrinterServiceType</pnpx:CompatibleId>
> <
http://schemas.microsoft.com/windows/pnpx/2005/10/%22%3Ehttp://schemas.microsoft.com/windows/2006/08/wdp/print/PrinterServiceType%3C/pnpx:CompatibleId%3E></Extension>
> > </wdp:Hosted>
> > </wdp:Relationship>
>
>
> > This section already includes another fix, that you will see
> > next, the pnpx elements, that must be in the device
> description
> >
> > To use this fragment in metadata.xml you have to define the
> > printer device namespace with the wprt prefix
> >
> > Can you please send the next mail to the mailinglist. So we
> > can continue this discussion in the mailing list. This
> has
the
> > advantage that if somebody else want's to implement a
> printer,
> > he can follow our discussion there and i don't have to tell
> > this several times.
> >
> > Regards
> > Elmar Zeeb
> >
> >>
> >> Thanks and regards,
> >> Sathya
> >>
>
>> --- On *Fri, 4/24/09, sathya sai
> /<
sai_eshwar@yahoo..co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_eshwar@yahoo..co.in>>/*
> >> wrote:
> >>
> >>
> >> From: sathya sai <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> >> Subject: Re: Regarding WS-Policy support on wsdl2h.exe
> >> To: "Elmar Zeeb" <
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>
> >> Cc: "sathya" <
sai_eshwar@yahoo.co..in> <
http://us..mc954.mail.yahoo.com/mc/compose?to=sai_eshwar@yahoo.co...in>>
> >> Date: Friday, April 24, 2009, 11:14 AM
> >>
> >>
> >> Hi Elmar,
> >>
> >> I could somehow get the network trace to
capture
> the XML
> >> packet exchange between vista client & the WSD server
> >> which is working. Please find it below.
> >>
> >> One thing which i could observe is ProbeMatch &
> >> ResolveMatch contains "
> >>
> <wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs>
> >> " data which was not happening (empty) with our
> >> ws4d-gSoap stack....
> >>
> >> As we don't have adequate documentation with us in
> >> ws4d-gsoap site. It would be great if you could suggest
> >> me an approach in using our APIs, If I need to achieve
> >>
the similar functionality with our ws4d-gSoap stack.
> >>
> >> Tomorrow I would try logging into IRC from my home,
> could
> >> you please let me know by which time would you be
> online.
> >>
> >> -----
> >>
> >> <?xml version="1.0"
encoding="UTF-8"?>
> >> <SOAP-ENV:Envelope
> >>
> xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
> >>
> xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> >>
> xmlns:wse="
http://schemas.xmlsoap.org/ws/2004/08/eventing"
> >>
xmlns:xop="
http://www.w3.org/2004/08/xop/include"
> >>
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> >>
> xmlns:wscn="
http://schemas.microsoft.com/windows/2006/08/wdp/scan"
> >>
> xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> >>
> xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> >>
> xmlns:trn=
http://schemas.xmlsoap.org/ws/2004/09/transfer> >>
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print">
> >>
<SOAP-ENV:Header>
> >>
> <wsa:Action>
http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action>
> >>
> <wsa:MessageID>urn:uuid:66ae878a-2f8d-11de-aebe-0000aa9e8e1a</wsa:MessageID>
> >>
> <wsa:RelatesTo>urn:uuid:fcd1881b-4488-428e-ae05-ade39e59a581</wsa:RelatesTo>
> >>
> <wsa:To>
http://schemas.xmlsoap..org/ws/2004/08/addressing/role/anonymous> <
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous></wsa:To>
> >> <wsd:AppSequence MessageNumber="9"
> >> InstanceId="1240438886"></wsd:AppSequence>
> >> </SOAP-ENV:Header>
> >> <SOAP-ENV:Body>
> >>
<wsd:ProbeMatches>
> >> <wsd:ProbeMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> >> </wsa:EndpointReference>
> >> <wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types>
> >>
> <wsd:XAddrs>
http://10.10..91.46:53202/webservices/wsd/TransferService> <
http://10.10.91.46:53202/webservices/wsd/TransferService></wsd:XAddrs>
> >> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> >> </wsd:ProbeMatch>
> >> </wsd:ProbeMatches>
> >> </SOAP-ENV:Body>
> >>
</SOAP-ENV:Envelope><?xml version="1.0"
> encoding="UTF-8"?>
> >>
> >>
> >>
> >> <SOAP-ENV:Envelope
> >>
> xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
> >>
> xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> >>
> xmlns:wse="
http://schemas.xmlsoap..org/ws/2004/08/eventing> <
http://schemas.xmlsoap.org/ws/2004/08/eventing>"
> >> xmlns:xop="
http://www.w3.org/2004/08/xop/include"
> >>
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> >>
> xmlns:wscn="
http://schemas.microsoft.com/windows/2006/08/wdp/scan"
> >>
> xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> >>
> xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> >>
>
xmlns:trn=
http://schemas.xmlsoap..org/ws/2004/09/transfer> <
http://schemas.xmlsoap.org/ws/2004/09/transfer>
> >>
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print">
> >> <SOAP-ENV:Header>
> >>
> <wsa:Action>
http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action>
> >>
> <wsa:MessageID>urn:uuid:66b76bc0-2f8d-11de-aebe-0000aa9e8e1a</wsa:MessageID>
> >>
> <wsa:RelatesTo>urn:uuid:ce6d377f-f6f6-44ed-9331-150ec8c53411</wsa:RelatesTo>
> >>
> <wsa:To>
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> >> <wsd:AppSequence MessageNumber="11"
>
>> InstanceId="1240438886"></wsd:AppSequence>
> >> </SOAP-ENV:Header>
> >> <SOAP-ENV:Body>
> >> <wsd:ProbeMatches>
> >> <wsd:ProbeMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> >>
</wsa:EndpointReference>
> >> <wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types>
> >>
> <wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs>
> >> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> >> </wsd:ProbeMatch>
> >> </wsd:ProbeMatches>
>
>> </SOAP-ENV:Body>
> >> </SOAP-ENV:Envelope><?xml version="1.0"
> encoding="UTF-8"?>
> >>
> >>
> >>
> >> <SOAP-ENV:Envelope
> >>
> xmlns:SOAP-ENV="
http://www.w3.org/2003/05/soap-envelope"
>
>>
> xmlns:SOAP-ENC="
http://www.w3.org/2003/05/soap-encoding"
> >>
> xmlns:wse="
http://schemas.xmlsoap.org/ws/2004/08/eventing"
> >> xmlns:xop="
http://www.w3.org/2004/08/xop/include"
> >>
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> >>
> xmlns:wscn="
http://schemas.microsoft.com/windows/2006/08/wdp/scan"
> >>
> xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"
> >>
> xmlns:wsd="
http://schemas.xmlsoap.org/ws/2005/04/discovery"
> >>
>
xmlns:trn=
http://schemas.xmlsoap.org/ws/2004/09/transfer> >>
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print">
> >> <SOAP-ENV:Header>
> >>
> <wsa:Action>
http://schemas.xmlsoap.org/ws/2005/04/discovery/ResolveMatches</wsa:Action>
> >>
> <wsa:MessageID>urn:uuid:6f030bb8-2f8d-11de-aebe-0000aa9e8e1a</wsa:MessageID>
> >>
> <wsa:RelatesTo>urn:uuid:f2567a08-aead-42cc-b308-10a3b4f4f227</wsa:RelatesTo>
> >>
> <wsa:To>
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
> >> <wsd:AppSequence MessageNumber="12"
> >> InstanceId="1240438886"></wsd:AppSequence>
>
>> </SOAP-ENV:Header>
> >> <SOAP-ENV:Body>
> >> <wsd:ResolveMatches>
> >> <wsd:ResolveMatch>
> >> <wsa:EndpointReference>
> >>
> <wsa:Address>uuid:97cba564-20bf-11de-90de-0000aa9e8e1a</wsa:Address>
> >> </wsa:EndpointReference>
> >>
<wsd:Types>wsdp:Device wprt:PrintDeviceType</wsd:Types>
> >>
> <wsd:XAddrs>
http://10.10.91.46:53202/webservices/wsd/TransferService</wsd:XAddrs>
> >> <wsd:MetadataVersion>1</wsd:MetadataVersion>
> >> </wsd:ResolveMatch>
> >> </wsd:ResolveMatches>
> >> </SOAP-ENV:Body>
> >>
</SOAP-ENV:Envelope>
> >>
> >> Thanks and regards,
> >> Sathya
> >>
> >> --- On *Tue, 4/21/09, Elmar Zeeb
> >> /<
elmar..zeeb@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>/*
> wrote:
> >>
> >>
> >> From: Elmar Zeeb <
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>
> >> Subject: Re: Regarding WS-Policy support on
> wsdl2h.exe
> >>
To: "sathya sai" <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> >> Date: Tuesday, April 21, 2009, 6:56 PM
> >>
> >> sathya sai schrieb:
> >>>
> >>> Hi
Elmar,
> >>>
> >>> Thanks a lot for your continous help towards me on
> >>> this. I am really thankful for it.
> >>>
> >>> Looks like IRC port is disabled here due to some
> >>> security constraints . I would somehow try my best
> >>>
to enable them.
> >>>
> >>> As suggested by you, I would now start
> ignoring the
> >>> below warnings on WS-Policy framework.
> >>>
> >>> As mentioned in my previous mail, I am now in the
> >>> process of implementing the Microsoft's printer
>
>>> device specification with the our ws4d-gSoap stack
> >>>
> (
http://www.microsoft.com/whdc/connect/rally/rallywsd.mspx> >>>
> <
http://www.microsoft.com/whdc/connect/rally/rallywsd.mspx>),
> >>> I could see that Microsoft have provided two WSDL
> >>>
file, one for PrinterDevice.wsdl &
> PrintService.wsdl...
> >>>
> >>> The *PrinterDevice.wsdl* has only the publishes
> >>> *PrintDeviceType* device type (mentioned in my
> below
> >>> mail) & *PrintService.wsdl* has all the
> definitions
> >>> of all printer services(such as
createjob,
> startJob...).
> >>>
> >>> Now how do you suggest me to use these two wsdl
> >>> files with our ws4d-gSoap stack ...As I
> couldn't get
> >>> any specific document on this, could you
> please let
> >>> me know your thoughts on the same.
> >>>
> >>> Meanwhile, this there any user/developer mailing
> >>> list for our ws4d-gSoap.
> >>>
> >> I created two Mailinglists for ws4d-gsoap. See
> >>
>
http://trac.e-technik.uni-rostock.de/projects/ws4d-gsoap/wiki/MailingLists> >> for more
information.
> >>
> >> Regards,
> >> Elmar Zeeb
> >>>
> >>> Thanks and regards,
> >>> Sathya
> >>>
> >>> --- On *Mon, 4/20/09, Elmar Zeeb
> >>> /<
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>/*
> wrote:
> >>>
> >>>
> >>> From: Elmar Zeeb
> <
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>
> >>> Subject: Re: Regarding WS-Policy support on
> >>> wsdl2h.exe
> >>> To: "sathya sai" <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> >>>
Date: Monday, April 20, 2009, 8:25 PM
> >>>
> >>> sathya sai schrieb:
> >>>>
> >>>> Hi Elmar,
> >>>>
> >>>> Thanks a lot responding to me on this
> >>>>
> >>>> > You should use the latest version in the
> >>>> subversion repository.
> >>>>
> >>>> Do you mean the latest subversion of
> ws4d-gsoap
> >>>> or gsoap. I am presently using
> >>>>
ws4d-gsoap-0.7.src & gsoap_2.7.13.
> >>>>
> >>> The latest version of ws4d-gsoap in the
> >>> subversion repository in trunk.
> >>>>
> >>>> > This should be no problem. The policy
> >>>> indicates the required conformance with dpws.
> >>>>
As > ws4d-gsoap conforms with dpws, we can
> >>>> ignore this.
> >>>>
> >>>> If I ignore them, I am getting an empty
> header
> >>>> file. As I am new to this XML world, I am not
> >>>> sure if this is right. Could you please
>
look at
> >>>> my WSDL file (which is been provided by
> >>>> Microsoft in the below specified URL) and let
> >>>> me know if you feel that I am missing
> anything
> >>>> on this regards. My actual intention is to
> >>>> develop, printer device/service using our
>
>>>> ws4d-gSoap stack & ensure that its comptible
> >>>> with the vista WSD client.
> >>>>
> >>> If the header file is empty, there is another
> >>> problem. soapcpp2, the code generator of gsoap
> >>> has not the best usability. I know that
> another
> >>>
user of ws4d-gsoap already is implementing
> this
> >>> specification with ws4d-gsoap - so this should
> >>> work. If this is the first time you use gsoap,
> >>> you may first get familiar with gsoap.
> >>> ws4d-gsoap makes heavy use of gsoap. You
> can ask
> >>>
me on IRC of course :-)
> >>>>
> >>>> > You should contact us at our ws4d irc
> channel
> >>>> on quakenet. Then i can help you directly.
> >>>> I am from India and I have not used quaknet.
> >>>> Could you please let me know the exact URL of
> >>>> quaknet
which I should use to contact/post
> >>>> query regarding this.
> >>>>
> >>> This is an irc server. You can use XChat on
> >>> Linux or mIRC on Windows. The quakenet server
> >>> should be already in the list of irc severs.
> >>> Simply connect to this server and join the
> ws4d
>
>>> channel. If you need more detailed explanation
> >>> how to use IRC, you can ask me by mail.
> >>>>
> >>>> Thanks a lot again.
> >>>>
> >>>> Regards,
> >>>>
Sathya
> >>>>
> >>>>
> >>>> --- On *Mon, 4/20/09, Elmar Zeeb
> >>>> /<
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>/*
> wrote:
>
>>>>
> >>>>
> >>>> From: Elmar Zeeb
> <
elmar...@uni-rostock.de> <
http://us.mc954.mail...yahoo.com/mc/compose?to=elmar...@uni-rostock.de>>
> >>>> Subject: Re: Regarding WS-Policy
> support on
> >>>>
wsdl2h.exe
> >>>> To: "sathya sai"
> <
sai_e...@yahoo.co.in> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sai_e...@yahoo.co.in>>
> >>>> Date: Monday, April 20, 2009, 12:44 PM
> >>>>
> >>>>
sathya sai schrieb:
> >>>>> Hi Developers,
> >>>>> I am presently in the process of
> >>>>> developing a Printer device/service
> using
> >>>>> ws4d-gSoap stack & to be compatible
> >>>>> against Microsoft vista's WSD
client
> >>>>>
> >>>> You should use the latest version in the
> >>>> subversion repository.
> >>>>>
> (
http://blogs.technet.com/askperf/archive/2008/02/11/ws2008-the-wsd-port-monitor.aspx).
> >>>>> My printer device/service
would
> follow the
> >>>>> specification/schema as mentioned in
> >>>>>
>
http://www.microsoft.com/whdc/connect/rally/rallywsd.mspx.
> >>>>>
> >>>>> Now the problem is; when I try to run
> >>>>>
"wsdl2h.exe" against the Microsoft's
> >>>>> WSDPrintDevice.wsdl (schema is as
> >>>>> specified below) as mentioned in your
> >>>>> "ws4d-gsoap-refman.pdf" manual, I am
> >>>>> getting the following warning msg
> from it
> >>>>>
& the header file is also not
> generated as
> >>>>> expected.
> >>>>>
> >>>> You won't be able to use the generated
> >>>> header file as is. The schemas use a
> lot of
> >>>> xml:any elements that require manual
>
>>>> adaptions in the header files
> generated by
> >>>> gSOAP.
> >>>>> ---------
> >>>>> $ ./wsdl2h.exe -c -n acs.gsoap
> >>>>> WSDPrintDevice.wsdl
> >>>>>
** The gSOAP WSDL parser for C and
> C++ 1.2.13
> >>>>> ** Copyright (C) 2000-2009 Robert van
> >>>>> Engelen, Genivia Inc.
> >>>>> ** All Rights Reserved. This product is
> >>>>> provided "as is", without any warranty.
> >>>>>
** The gSOAP WSDL parser is released
> >>>>> under one of the following two licenses:
> >>>>> ** GPL or the commercial license by
> >>>>> Genivia Inc. Use option -l for more
> info.
> >>>>> Saving WSDPrintDevice.h
> >>>>>
Reading type definitions from type map
> >>>>> file 'typemap.dat'
> >>>>> Reading file 'WSDPrintDevice.wsdl'...
> >>>>> Warning: element 'wsp:Policy' at
> level 1 w
> >>>>> as not recognized and will be ignored
> >>>>>
Warning: element
> 'wsp:PolicyReference' at
> >>>>> level 2 was not recognized and will be
> >>>>> ignored
> >>>>>
> >>>> This should be no problem. The policy
> >>>> indicates the required conformance with
> >>>>
dpws. As ws4d-gsoap conforms with
> dpws, we
> >>>> can ignore this.
> >>>>> done reading 'WSDPrintDevice.wsdl'
> >>>>> To complete the process, compile with:
> >>>>> soapcpp2 WSDPrintDevice.h
> >>>>>
> >>>>>
sathyas@sathyas
> >>>>>
> <
http://us.mc954.mail.yahoo.com/mc/compose?to=sathyas@sathyas>
> >>>>>
> /cygdrive/d/WSD/gsoap-binaries/gsoap_2.7.13/gsoap-2.7/gsoap/WS
> >>>>> $
> >>>>> -------------------
>
>>>>> My gSoap stack version is 2.7.13.
> Does it
> >>>>> mean that WSDL's WS-Policy framework is
> >>>>> not support by "wsdl2.h.exe". If yes,
> >>>>> could you please suggest me an
> alternative
> >>>>> for
this.
> >>>>> ----
> >>>>> WSDPrintDevice.wsdl file,
> >>>>> <wsdl:definitions
> >>>>>
> xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
> >>>>>
> >>>>>
> xmlns:wsoap12="
http://schemas.xmlsoap.org/wsdl/soap12/"
> >>>>>
> >>>>>
> xmlns:wsdp="
http://schemas.xmlsoap.org/ws/2006/02/devprof"
> >>>>>
> >>>>>
> xmlns:wsp="
http://schemas..xmlsoap.org/ws/2004/09/policy> >>>>>
> <
http://schemas.xmlsoap.org/ws/2004/09/policy>"
> >>>>>
> >>>>>
> xmlns:wsu="
http://docs..oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
> >>>>>
> >>>>>
> xmlns:wprt="
http://schemas.microsoft.com/windows/2006/08/wdp/print"
> >>>>>
> >>>>>
> targetNamespace="
http://schemas.microsoft.com/windows/2006/08/wdp/print"
> >>>>> name="WSDPrintDevice">
> >>>>> <wsp:Policy wsu:Id="DevicePolicy">
> >>>>>
<wsdp:Profile />
> >>>>> </wsp:Policy>
> >>>>> <wsdl:portType
> name="PrintDeviceType" />
> >>>>> <wsdl:binding
> >>>>> name="PrinterSoapBinding"
> >>>>>
type="wprt:PrintDeviceType" >
> >>>>> <wsoap12:binding
> style="document"
> >>>>>
> transport="
http://schemas.xmlsoap.org/soap/http"
> >>>>> />
> >>>>> <wsp:PolicyReference
>
>>>>> URI="#DevicePolicy"
> wsdl:required="true" />
> >>>>> </wsdl:binding>
> >>>>> </wsdl:definitions>
> >>>>> ------
> >>>>> Could you please let me know with your
> >>>>>
suggestions by earlist.
> >>>>>
> >>>>> Thanks a lot in advance.
> >>>>>
> >>>>> Regards,
> >>>>> Sathya
> >>>>>
>
>>>>>
> >>>> You should contact us at our ws4d irc
> >>>> channel on quakenet. Then i can help you
> >>>> directly.
> >>>>
> >>>> Regards,
> >>>> Elmar Zeeb
>
>>>>
> >>>> --
> >>>>
> *******************************************************************************
> >>>> Dipl.-Inf. Elmar Zeeb
> >>>> Universität Rostock, Fakultät f.
> Informatik und Elektrotechnik
> >>>>
Institut f. Angewandte
> Mikroelektronik und Datentechnik
> >>>> University of Rostock, Faculty of
> CS and EE
> >>>> Institute of Applied
> Microelectronics and Computer Engineering,
> >>>> 18051 Rostock
> >>>> Deutschland/Germany
>
>>>> Tel. :
++49 (0)381 498 - 7262> >>>> Fax :
++49 (0)381 498 - 7252> >>>> Email:
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar.zeeb@uni-rostock..de>
> >>>>
www :
>
http://www.imd.uni-rostock.de/,
http://www.ws4d.org/> >>>>
> *******************************************************************************
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
--
> >>>
> *******************************************************************************
> >>> Dipl.-Inf. Elmar Zeeb
> >>> Universität Rostock, Fakultät f.
> Informatik und Elektrotechnik
> >>> Institut f. Angewandte Mikroelektronik
> und Datentechnik
> >>>
University of Rostock, Faculty of CS and EE
> >>> Institute of Applied Microelectronics
> and Computer Engineering,
> >>> 18051 Rostock
> >>> Deutschland/Germany
> >>> Tel. :
++49 (0)381 498 - 7262> >>> Fax :
++49 (0)381 498 -
7252
> >>> Email:
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar.zeeb@uni-rostock..de>
> >>> www :
http://www.imd.uni-rostock.de/,
>
http://www.ws4d.org/> >>>
> *******************************************************************************
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >>
> *******************************************************************************
> >> Dipl.-Inf. Elmar Zeeb
>
>> Universität Rostock, Fakultät f. Informatik
> und Elektrotechnik
> >> Institut f. Angewandte Mikroelektronik und
> Datentechnik
> >> University of Rostock, Faculty of CS and EE
> >> Institute of Applied Microelectronics and
> Computer Engineering,
> >> 18051 Rostock
> >>
Deutschland/Germany
> >> Tel. :
++49 (0)381 498 - 7262> >> Fax :
++49 (0)381 498 - 7252> >> Email:
elmar...@uni-rostock.de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar..zeeb@uni-rostock.de>
> >> www :
http://www.imd.uni-rostock.de/,
>
http://www.ws4d.org/> >>
> *******************************************************************************
> >>
> >>
> >>
> >>
> >
> >
> > --
> >
>
*******************************************************************************
> > Dipl.-Inf. Elmar Zeeb
> > Universität Rostock, Fakultät f. Informatik und
> Elektrotechnik
> > Institut f. Angewandte Mikroelektronik und Datentechnik
> > University of Rostock, Faculty of CS and EE
> > Institute of Applied Microelectronics and Computer
> Engineering,
> > 18051 Rostock
> >
Deutschland/Germany
> > Tel. :
++49 (0)381 498 - 7262> > Fax :
++49 (0)381 498 - 7252> > Email:
elmar.zeeb@uni-rostock..de> <
http://us.mc954.mail.yahoo.com/mc/compose?to=elmar.zeeb@uni-rostock..de>
> > www :
http://www.imd.uni-rostock.de/,
>
http://www.ws4d.org/> >
> *******************************************************************************
> >
> >
> >
> >
>
>
> --
> *******************************************************************************
> Dipl.-Inf. Elmar Zeeb
> Universität Rostock, Fakultät f. Informatik und Elektrotechnik
> Institut f. Angewandte Mikroelektronik und Datentechnik
>
University of Rostock, Faculty of CS and EE
> Institute of Applied Microelectronics and Computer Engineering,
> 18051 Rostock
> Deutschland/Germany
> Tel. :
++49 (0)381 498 - 7262> Fax :
++49 (0)381 498 - 7252> Email:
elmar...@uni-rostock.de> <
http://us.mc954..mail.yahoo.com/mc/compose?to=elmar...@uni-rostock.de>
> www :
http://www.imd.uni-rostock.de/,
http://www.ws4d.org/> *******************************************************************************
>
>
>
> >
--
*******************************************************************************
Dipl.-Inf. Elmar Zeeb
Universität Rostock, Fakultät f. Informatik und Elektrotechnik
Institut f. Angewandte Mikroelektronik und Datentechnik
University of Rostock, Faculty of CS and EE
Institute of Applied Microelectronics and Computer Engineering,
18051 Rostock
Deutschland/Germany
Tel. :
++49 (0)381 498 - 7262 Fax :
++49 (0)381 498 - 7252 Email:
elmar...@uni-rostock.de www :
http://www.imd.uni-rostock.de/,
http://www.ws4d.org/*******************************************************************************
