On Oct 24, 2013, at 10:42 AM, Daniel Kulp <[email protected]> wrote: > On Oct 24, 2013, at 10:05 AM, Pampolini Matteo > <[email protected]> wrote: >> thanks for your reply, I downloaded and tested snapshot >> 2.7.8-20131023.085812-20 but now, even with >> WCF proxy stopped, I'm not able to find any device, am I doing anything >> wrong? > > That’s not good. Not sure what would cause that. Can you wireshark things > to make sure things are responding properly?
Actually, any chance you can put a breakpoint on line 356 of WSDiscoveryClient? I’d like to know if the callback is at least being called. If you cannot put breakpoint on the stuff in the jar, can you just grab the source for that one class from: http://svn.apache.org/repos/asf/cxf/branches/2.7.x-fixes/services/ws-discovery/ws-discovery-api/src/main/java/org/apache/cxf/ws/discovery/WSDiscoveryClient.java and add that to your project (and modify the package) and call that instead of the CXF version? I’d definitely like to make sure the handler is properly called. If not, then I know the issue is down in the UDPConduit. If it is called, I’d like to know what’s going on. Likely some sort of exception, but not really sure. (although, looking at that, we probably SHOULD be at least saving the first exception and if size() is 0 at the end and there is an exception, throw it) Need to think a bit more. If ONE (or more) services return a fault, but at least one service does not, what should be the right behavior? Return the one that didn’t and ignore the faults? Maybe provide an optional List<Exception> to record any faults? Hmm….. Dan > > Dan > >> >> Regards, Matteo >> >> On 23/10/2013 22:21, Daniel Kulp wrote: >>> On Oct 23, 2013, at 8:37 AM, Pampolini Matteo >>> <[email protected]> wrote: >>> >>>> Hi Dan, >>>> >>>> did you find some time to look at this issue? >>> Just fixed, I think. Can you give the next snapshots a try? >>> >>> Dan >>> >>> >>> >>>> Thanks, Matteo >>>> >>>> >>>> -------- Original Message -------- >>>> Subject: Re: WS-Discovery does not work with a WCF discovery proxy >>>> (should be fixed in CXF Jira) >>>> Date: Wed, 16 Oct 2013 11:21:38 +0200 >>>> From: Pampolini Matteo <[email protected]> >>>> To: [email protected] <[email protected]> >>>> CC: Daniel Kulp <[email protected]> >>>> >>>> Hi Dan, >>>> >>>> many thanks for your quick reply. Please find attached both exceptions >>>> traces (I had to enable them in WSDiscoveryClient code) and Wireshark >>>> captures. The address from which I start WS-Discovery is 172.19.121.75 >>>> while the proxy is hosted at 172.19.121.69. You can note that the proxy >>>> replies with SOAP fault messages, but after that all ONVIF devices on >>>> the network reply by themselves, then I expected my client to receive >>>> and process the replies anyway. >>>> >>>> I also tried directly with the proxy without success. >>>> >>>> Regards, Matteo >>>> >>>> On 15/10/2013 18:58, Daniel Kulp wrote: >>>>> On Oct 15, 2013, at 12:04 PM, Pampolini Matteo >>>>> <[email protected]> wrote: >>>>> >>>>>> Hello there, >>>>>> >>>>>> I'm using CXF WS-Discovery to find ONVIF devices on my network. >>>>>> >>>>>> After a patch from Dan, included from version 2.7.5, that allows to set >>>>>> discovery version to 1.0 everything >>>>>> was fine, but now I'm facing a new issue if a discovery proxy developed >>>>>> with .NET WCF is in the same network, >>>>>> I get some exceptions (I recompiled CXF with some custom debug prints) >>>>>> and no device is found. Shutting down >>>>>> the proxy everything works as expected. >>>>> I'd likely need to at least see what the exceptions are. Ideally, >>>>> could you wireshark the probe and responses and see what is coming back. >>>>> >>>>> One thought is that the proxy is sending back a Hello and thus the client >>>>> is flipping to managed mode (to use the proxy), but the proxy isn't then >>>>> sending any information back or CXF isn't waiting for it and it's getting >>>>> lost. What happens if you do a second probe with the same client? In >>>>> that case, the probe should ONLY go to the proxy. >>>>> >>>>> What happens if you force the client to use the proxy right up front via >>>>> the constructor that takes the address? Use an address like >>>>> "soap.udp://proxy.hostname:3702". In that case, the probe should just >>>>> go to the proxy immediately. Does the proxy return the right >>>>> information? >>>>> >>>>> Not sure what else to suggest at this point. Would really need to the >>>>> packets and stack traces. >>>>> >>>>> Dan >>>>> >>>>> >>>>> >>>>>> It seems a similar, not to say equal, issue was opened on CXF Jira with >>>>>> number 4955 that should be fixed now, >>>>>> but this is not my case. Since in issue description the WS-Discover >>>>>> version mentioned is 1.1, could it be that >>>>>> the issue is still present when setting version 1.0, as requested by >>>>>> ONVIF specs? >>>>>> >>>>>> Any help is very appreciated, thanks in advance, >>>>>> >>>>>> Matteo >>>>>> >>>>>> >>>>>> This email and any attachments are confidential to the intended >>>>>> recipient and may also be privileged. If you are not the intended >>>>>> recipient please delete it from your system and notify the sender. You >>>>>> should not copy it or use it for any purpose nor disclose or distribute >>>>>> its contents to any other person. >>>>>> Questa e-mail e tutti i suoi allegati sono da intendersi inviati in via >>>>>> riservata all'effettivo destinatario e possono essere soggetti a >>>>>> restrizioni legali. Se non siete l'effettivo destinatario o avete >>>>>> ricevuto il messaggio per errore siete pregati di cancellarlo dal vostro >>>>>> sistema e di avvisare il mittente. E' vietata la duplicazione, l'uso a >>>>>> qualsiasi titolo, la divulgazione o la distribuzione dei contenuti di >>>>>> questa e-mail a qualunque altro soggetto. >>>>>> >>>>>> Prima di stampare questa comunicazione consideratene, per favore, >>>>>> l'impatto ambientale >>>>>> Please consider the environment before printing this email >>>> >>>> >>>> >>>> This email and any attachments are confidential to the intended recipient >>>> and may also be privileged. If you are not the intended recipient please >>>> delete it from your system and notify the sender. You should not copy it >>>> or use it for any purpose nor disclose or distribute its contents to any >>>> other person. >>>> Questa e-mail e tutti i suoi allegati sono da intendersi inviati in via >>>> riservata all'effettivo destinatario e possono essere soggetti a >>>> restrizioni legali. Se non siete l'effettivo destinatario o avete ricevuto >>>> il messaggio per errore siete pregati di cancellarlo dal vostro sistema e >>>> di avvisare il mittente. E' vietata la duplicazione, l'uso a qualsiasi >>>> titolo, la divulgazione o la distribuzione dei contenuti di questa e-mail >>>> a qualunque altro soggetto. >>>> >>>> Prima di stampare questa comunicazione consideratene, per favore, >>>> l'impatto ambientale >>>> Please consider the environment before printing this email >>>> <discovery.zip> >> >> This email and any attachments are confidential to the intended recipient >> and may also be privileged. If you are not the intended recipient please >> delete it from your system and notify the sender. You should not copy it or >> use it for any purpose nor disclose or distribute its contents to any other >> person. >> Questa e-mail e tutti i suoi allegati sono da intendersi inviati in via >> riservata all'effettivo destinatario e possono essere soggetti a restrizioni >> legali. Se non siete l'effettivo destinatario o avete ricevuto il messaggio >> per errore siete pregati di cancellarlo dal vostro sistema e di avvisare il >> mittente. E' vietata la duplicazione, l'uso a qualsiasi titolo, la >> divulgazione o la distribuzione dei contenuti di questa e-mail a qualunque >> altro soggetto. >> >> Prima di stampare questa comunicazione consideratene, per favore, l'impatto >> ambientale >> Please consider the environment before printing this email > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
