zdco / java-ws-discovery Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/java-ws-discovery
License: GNU Lesser General Public License v3.0
Automatically exported from code.google.com/p/java-ws-discovery
License: GNU Lesser General Public License v3.0
What steps will reproduce the problem?
1. publish an endpoint a qname and a scope set
2. findAll returns the endpoint
3. find(qname, scope, timeout) does not return the endpoint
4. find(qname, scope, rfc2396 matcher, timeout) does not return the endpoint
5. find(qname, timeout) does not return the endpoint
What is the expected output? What do you see instead?
expecting to find the endpoint
What version of the product are you using? On what operating system?
windows7 x64, x86 sun jdk
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 29 Mar 2012 at 3:13
Hi,
I deployed webservice in WAS7 succuessfully.
I ran the examples and with correct end point.
I did not receive any out put, otherthan sysout messages.
No exception not things, its works fine, but no results.
What might be the cause...???
Regards
kiran.
Original issue reported on code.google.com by [email protected]
on 22 Jun 2012 at 1:59
What steps will reproduce the problem?
1. Create a war file targeted at deployment to jboss with j2ee class loading
option turned on
2. Create a singleton class that wraps around the provided wsdiscovery server
3. Create a servlet context listener that starts the ws-discovery singlton class
4. Publish some endpoints in the context listener
5. Use a command line client to probe for endpoints
What is the expected output? What do you see instead?
Serialization issue. When running in jboss, the jboss web services stack
supplies the MessageFactory and thus handles the .writeTo(OutputStream)
function. Long story short, the contents of ProbeMatches is empty, even though
it is added to the ProbeMatches object.
What version of the product are you using? On what operating system?
0.2 windows 7 with jboss 5.1.2
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 9 Apr 2012 at 3:15
If a Hello is sent without any Scopes, the service will NPE:
java.lang.NullPointerException
at com.ms.wsdiscovery.standard11.WsDiscoveryS11Utilities.createWsDiscoveryScopesObject(WsDiscoveryS11Utilities.java:201)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11Utilities.createWsDiscoveryService(WsDiscoveryS11Utilities.java:85)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11Utilities.storeJAXBObject(WsDiscoveryS11Utilities.java:293)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11DispatchThread.recvHello(WsDiscoveryS11DispatchThread.java:262)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11DispatchThread.dispatch(WsDiscoveryS11DispatchThread.java:737)
at com.ms.wsdiscovery.common.WsDiscoveryDispatchThread.run(WsDiscoveryDispatchThread.java:296)
The schema states that scopes are minOccurs=0 and thus it should be acceptable
for there to not be any scopes present.
Original issue reported on code.google.com by [email protected]
on 16 Aug 2012 at 7:21
What steps will reproduce the problem?
1. I creat a WsDiscoveryPublishJaxWS like in the calculator Example in the wiki
2. I start Tomcat v7 on localhost
3. I run my Publich Class as a Java Application on Eclipse J2EE
What is the expected output? What do you see instead?
I shoudn't get this list of errors at execution:
-------------------------------------------------------------
SEVERE: Unable to create WS-Discovery SOAP message.
com.ms.wsdiscovery.network.exception.WsDiscoveryNetworkException: Unable to
create WS-Discovery SOAP message.
at com.ms.wsdiscovery.network.DispatchThread.dispatch(DispatchThread.java:697)
at com.ms.wsdiscovery.network.DispatchThread.run(DispatchThread.java:814)
Caused by: com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to
unmarshal SOAP document.
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessage.parseSoap(WsdSOAPMessage.java:225)
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessage.<init>(WsdSOAPMessage.java:161)
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessageBuilder.createWsdSOAPMessage(WsdSOAPMessageBuilder.java:93)
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessageBuilder.createWsdSOAPMessage(WsdSOAPMessageBuilder.java:83)
at com.ms.wsdiscovery.network.DispatchThread.dispatch(DispatchThread.java:695)
... 1 more
-------------------------------------------------------------
What version of the product are you using? On what operating system?
I am using java-ws-discovery-0.2 on a MAC OS version 10.6.7
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 3 Feb 2012 at 11:06
Hello,
the website says it it released under the LGPL while the LICENSE.txt in the
download says its GPL.
Please make it consistent.
Stephan
Original issue reported on code.google.com by [email protected]
on 11 Feb 2009 at 12:25
What steps will reproduce the problem?
1. Copy/paste the code from
2.
3.
Hi!
I have a WsDiscoveryNetworkException when I'm using java-ws-discovery inside an
OSGI bundle. I have pasted the code of the WsDiscoveryExample at
http://code.google.com/p/java-ws-discovery/wiki/WsDiscoveryFinderExample inside
the start() method of my bundle.
I'm expecting the discovery service to succeed its multicast operations and
return results about Web services on a specified target.
My OS is Windows 7. I am using the distributed provided by the ZIP file of the
Google Code site.
This is my code:
public void start(BundleContext context) throws Exception
{
System.out.println("Creating new finder-instance...");
WsDiscoveryFinder finder = new WsDiscoveryFinder();
/**
* Search for a specific service
*/
{
// Describe the port type of the service we are looking for. Namespace is optional.
//QName myPortType = new QName("http://calculatorservice.examples.wsdiscovery.ms.com/", "CalculatorService");
QName myPortType = new QName("http://132.210.47.44/", "CalculatorService");
// Search for with 5 second timeout...
System.out.println("Searching for service with port type \"" + myPortType.toString() + "\"");
IWsDiscoveryServiceCollection result = finder.find(myPortType, 5000);
// Display the results.
System.out.println("** Discovered services: **");
for (WsDiscoveryService service : result) {
// Print service info
System.out.println(service.toString());
System.out.println("---");
}
}
/**
* Search for any service
*/
{
System.out.println("Searching for all services (2 sec).");
IWsDiscoveryServiceCollection result = finder.findAll(2000);
// Display the results.
System.out.println("** Discovered services: **");
for (WsDiscoveryService service : result) {
// Print service info
System.out.println(service.toString());
System.out.println("---");
}
}
// Stop finder
finder.done();
}
This is the output I have:
Welcome to Felix
================
Creating new finder-instance...
Searching for service with port type "{http://132.210.47.44/}CalculatorService"
11-Oct-2010 3:16:27 PM com.ms.wsdiscovery.logger.WsDiscoveryLogger fine
FINE: Multicasting probe (not using proxy).
com.ms.wsdiscovery.exception.WsDiscoveryNetworkException: Unable to multicast
probe
at com.ms.wsdiscovery.standard11.WsDiscoveryS11DispatchThread.sendProbe(WsDiscoveryS11DispatchThread.java:159)
at com.ms.wsdiscovery.WsDiscoveryServer.probe(WsDiscoveryServer.java:150)
ERROR: Error starting
file:/C:/Users/Pierre-Alexandre/Documents/NetBeansProjects/Prototype3Client/targ
et/Prototype3Client-1.0-SNAPSHOT.jar (org.osgi.framework.BundleException:
Activator start error in bundle domus.usherbrooke.Prototype3Client [13].)
at com.ms.wsdiscovery.WsDiscoveryFinder.find(WsDiscoveryFinder.java:151)
at com.ms.wsdiscovery.WsDiscoveryFinder.find(WsDiscoveryFinder.java:213)
at com.ms.wsdiscovery.WsDiscoveryFinder.find(WsDiscoveryFinder.java:324)
at domus.usherbrooke.prototype3client.Prototype3ClientActivator.start(Prototype3ClientActivator.java:32)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:640)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1700)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1622)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Unknown Source)
Caused by: com.skjegstad.soapoverudp.exceptions.SOAPOverUDPException: Unable to
convert SOAPMessage to XML.
at com.skjegstad.soapoverudp.messages.SOAPOverUDPMessage.toString(SOAPOverUDPMessage.java:406)
at com.skjegstad.soapoverudp.SOAPOverUDP.sendMulticast(SOAPOverUDP.java:83)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11DispatchThread.sendProbe(WsDiscoveryS11DispatchThread.java:157)
... 11 more
Caused by: com.skjegstad.soapoverudp.exceptions.SOAPOverUDPException: Unable to
create JAXB instance: com.skjegstad.soapoverudp.jaxb.wsaddressing200508
at com.skjegstad.soapoverudp.SOAPOverUDPUtilities.createJAXBContext(SOAPOverUDPUtilities.java:48)
at com.skjegstad.soapoverudp.datatypes.SOAPOverUDPNamespaces.getJAXBContext(SOAPOverUDPNamespaces.java:60)
at com.skjegstad.soapoverudp.datatypes.SOAPOverUDPNamespaces.getUnmarshaller(SOAPOverUDPNamespaces.java:73)
at com.skjegstad.soapoverudp.messages.SOAPOverUDPWSA200508Message.removeWSAHeader(SOAPOverUDPWSA200508Message.java:71)
at com.skjegstad.soapoverudp.messages.SOAPOverUDPWSA200508Message.saveWSAHeader(SOAPOverUDPWSA200508Message.java:118)
at com.skjegstad.soapoverudp.messages.SOAPOverUDPMessage.saveChanges(SOAPOverUDPMessage.java:173)
at com.ms.wsdiscovery.standard11.WsDiscoveryS11SOAPMessage.saveChanges(WsDiscoveryS11SOAPMessage.java:526)
at com.skjegstad.soapoverudp.messages.SOAPOverUDPMessage.toString(SOAPOverUDPMessage.java:398)
... 13 more
Caused by: javax.xml.bind.JAXBException:
"com.skjegstad.soapoverudp.jaxb.wsaddressing200508" doesnt contain
ObjectFactory.class or jaxb.index
at com.sun.xml.internal.bind.v2.ContextFactory.createContext(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.xml.bind.ContextFinder.newInstance(Unknown Source)
at javax.xml.bind.ContextFinder.find(Unknown Source)
at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
at com.skjegstad.soapoverudp.SOAPOverUDPUtilities.createJAXBContext(SOAPOverUDPUtilities.java:46)
... 20 more
Please help.
Original issue reported on code.google.com by [email protected]
on 11 Oct 2010 at 7:21
When Apache CXF creates soap messages with WS-Addressing header, the default is
to NOT put and of the namespace prefixes other than the SOAP prefix onto the
soap:Envelope or soap:Header elements. Instead it will define it directly on
the elements that need it:
<Action
xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-dd/ns
/discovery/2009/01/Hello</Action>
The method above only checks if the prefix is defined on the soap:Header
element and thus will reject the CXF generated messages which are proper
XML/SOAP messages.
Original issue reported on code.google.com by [email protected]
on 16 Aug 2012 at 4:17
What steps will reproduce the problem?
1. svn checkout
2. configure.bat
3. mvn install
What is the expected output? What do you see instead?
Path to dependency:
1) com.skjegstad:wsdiscovery-soap-lib:jar:1.0-SNAPSHOT
2) xerces:xercesImpl:jar:xerces-exificient
----------
1 required artifact is missing.
for artifact:
com.skjegstad:wsdiscovery-soap-lib:jar:1.0-SNAPSHOT
What version of the product are you using? On what operating system?
.2 beta on windows 7
Please provide any additional information below.
jdk 1.6.27
Original issue reported on code.google.com by [email protected]
on 1 Apr 2012 at 11:30
Using netcat to send a message to the local host in 3702 port, the receiver
unicast socket ignores the message
What steps will reproduce the problem?
1. Launch a discovery server
2. Place breakpoint in SOAPReceiverThread:118
3. Send a message to localhost:3702 --> nc -u localhost 3702
4. It does not stop in breakpoint.
What is the expected output? What do you see instead?
The message is not even discarded (but it should, since local messages are
discarded) because unicast socket does not receive the message.
What version of the product are you using? On what operating system?
Ubuntu 9.10
Eclipse 3.5
Java 1.6.0_15-b03
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 25 Nov 2009 at 9:04
What steps will reproduce the problem?
1. Get/build code from svn
2. use WsDiscoveryFactory.createService to build service
3. use service.getEndpointReference() to get initial information
4. use endpointReference.set..[ReferenceParameters, PortType, ServiceName]
to set values
I seem to be able to set the values but they do not seem to go out on the
network. Currently I am using the 'Microsoft Network Monitor 3.3' tool to
look at the message packets.
From the sample service I can publish using the example gui I see what
schema is used. With that information I build a sample message that
validates, see below.
<?xml version="1.0" encoding="UTF-8"?>
<Hello xmlns="http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
http://docs.oasis-open.org/ws-dd/discovery/1.1/os/wsdd-discovery-1.1-schema-os.x
sd">
<wsa:EndpointReference>
<wsa:Address>urn:uuid:be95c928-c065-443d-845a-44542ce9d2c9</wsa:Address>
<wsa:ReferenceParameters>
<anyThingCanGoHere>
<hereIsSomething/>
<hereIsAnotherThing/>
</anyThingCanGoHere>
</wsa:ReferenceParameters>
</wsa:EndpointReference>
<Types>service_Types</Types>
<Scopes>service_Scopes</Scopes>
<XAddrs>http://localhost:1234/service_Xaddrs</XAddrs>
<MetadataVersion>1</MetadataVersion>
</Hello>
Looking at my valid sample message I would expect to be able to populate
<wsa:ReferenceParameters> since it validates with the same schema. I also
notices that .setPortType(portType) and .setServiceName(serviceName) do not
seem to work either.
I can see that they are set in the logs
Starting WS-Discovery server...
Publishing service:
Address: urn:uuid:ea5ecdc9-b8af-4dd6-aea1-83076ce7bdce
PortType: {service_PortType_namespace}service_PortType
ServiceName.PortName: service_Name
ServiceName.Value: {service_NameQ_namespace}service_NameQ
Any: Other: (null)
Types: {service_Types_namespace}service_Types
XAddrs: http://localhost:1234/service_Xaddrs
Scopes: service_Scopes
Thanks for you help on this potential issue
Original issue reported on code.google.com by [email protected]
on 22 Jan 2010 at 8:47
What steps will reproduce the problem?
1.Checkout the baseline (HEAD)131
2.Run the install_exificient.sh under Ubuntu terminal
3.Create a Java project in Eclipse for the wsdiscovery-lib, which include the
wsdiscovery-soap-lib as well.
What is the expected output? What do you see instead?
When build the project, this dependant
com.ms.wsdiscovery.jaxb can't be resolved.
What version of the product are you using? On what operating system?
Using HEAD 131 on Ubuntu 10.03
Please provide any additional information below.
I checked the xercesImpl-xerces-exificient.jar, xml-apis-apis-exificient.jar
are generated under ~/.m2/... directory. Don't know how the Eclipse could use
them? I tried to add these jar files as library but it does not resolve the
issue.
Original issue reported on code.google.com by [email protected]
on 27 Nov 2012 at 9:51
Fix problem with Eclipse/m2e not being able to find a valid POM for these local
artifacts.
Original issue reported on code.google.com by [email protected]
on 15 Mar 2012 at 9:33
Attachments:
Greetings,
This is a great implementation. I found it advantageous over UDDI registry,
because, some services would not be registered in UDDI and it would be hard
to discover them.
I have an existing web service and want to find out, if there is any way to
add it to the network or start sending udp multicast, without making
changes to it.
I may/may not have the oppurtunity to write some interfaces or wrappers
over top of existing web service.
BTW, is there any forum where I can post my questions?
Thanks,
Ganesh.
Original issue reported on code.google.com by [email protected]
on 19 Mar 2010 at 5:46
What steps will reproduce the problem?
1. Downloaded the last tar
2. Generated JAR snapshot with dependencies
3. Tried to execute your examples, and Exception was sent.
What is the expected output? What do you see instead?
Output:
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger warning
ADVERTENCIA: Proxy address guessed as /192.168.10.81. Set proxyAddress to
override.
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger info
INFO: Proxy-service bound to 192.168.10.81 on port 60426 (not enabled)
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: Started Thread-0
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: Started receiver thread multicast_recv, listening on
0.0.0.0/0.0.0.0
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: Started sender thread multicast_send, sending from
0.0.0.0/0.0.0.0
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: Started sender thread unicast_send, sending from 0.0.0.0/0.0.0.0
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: Started receiver thread unicast_recv, listening on
0.0.0.0/0.0.0.0
Sending probe...
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger finer
MÁS FINA: sendProbe() Sending probe with @MatchBy=null
16-mar-2010 17:19:21 com.ms.wsdiscovery.logger.WsdLogger fine
FINA: Multicasting probe (not using proxy).
com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to create
JAXB instance: com.ms.wsdiscovery.xml.jaxb_generated
at com.ms.wsdiscovery.xml.WsdXMLBuilder.newInstance
(WsdXMLBuilder.java:98)
at com.ms.wsdiscovery.xml.WsdXMLBuilder.createMarshaller
(WsdXMLBuilder.java:110)
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessage.toSoap
(WsdSOAPMessage.java:298)
at com.ms.wsdiscovery.xml.soap.WsdSOAPMessage.toString
(WsdSOAPMessage.java:483)
at com.ms.wsdiscovery.network.NetworkMessage.<init>
(NetworkMessage.java:130)
at com.ms.wsdiscovery.network.DispatchThread.sendProbe
(DispatchThread.java:255)
at com.ms.wsdiscovery.network.DispatchThread.sendProbe
(DispatchThread.java:293)
at com.ms.wsdiscovery.WsDiscoveryServer.probe
(WsDiscoveryServer.java:119)
at WebServiceFinder.main(WebServiceFinder.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.intellij.rt.execution.application.AppMain.main
(AppMain.java:90)
Exception in thread "main" java.lang.NullPointerException
at com.ms.wsdiscovery.network.NetworkMessage.<init>
(NetworkMessage.java:119)
at com.ms.wsdiscovery.network.NetworkMessage.<init>
(NetworkMessage.java:130)
at com.ms.wsdiscovery.network.DispatchThread.sendProbe
(DispatchThread.java:255)
at com.ms.wsdiscovery.network.DispatchThread.sendProbe
(DispatchThread.java:293)
at com.ms.wsdiscovery.WsDiscoveryServer.probe
(WsDiscoveryServer.java:119)
at WebServiceFinder.main(WebServiceFinder.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.intellij.rt.execution.application.AppMain.main
(AppMain.java:90)
What version of the product are you using? On what operating system?
Windows 7
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 16 Mar 2010 at 4:22
I used WsDiscoveryFinderExample and made below changes:
QName myPortType = new QName("http://www.onvif.org/ver10/network/wsdl", "NetworkVideoTransmitter", "dn");
and it couldn't find axis onvif enabled camera (for specific service)
However I tried another program which is Onvif Device Manager
(http://sourceforge.net/projects/onvifdm/)
and this program finds the camera.
I compared created udp packets using Wireshark and there are slight differences
between them.
java-ws-discovery udp-data:
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery">
<env:Header>
<wsd:AppSequence InstanceId="1323359689465" MessageNumber="1" SequenceId="urn:uuid:bdfcafd1-39e0-4edb-a8f7-7ba9ea3e54f7"/>
<wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To>
<wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe</wsa:Action>
<wsa:MessageID>urn:uuid:4e8815f2-8c93-4550-9bbf-926d6936bbae</wsa:MessageID>
</env:Header>
<env:Body>
<wsd:Probe>
<wsd:Types xmlns:dn="http://www.onvif.org/ver10/network/wsdl">dn:NetworkVideoTransmitter</wsd:Types>
</wsd:Probe>
</env:Body>
</env:Envelope>
Onvif device manager udp-data:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe</a:Action>
<a:MessageID>urn:uuid:e8347b80-f991-4938-997f-3f8323514729</a:MessageID>
<a:ReplyTo>
<a:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">urn:schemas-xmlsoap-org:ws:2005:04:discovery</a:To>
</s:Header>
<s:Body>
<Probe xmlns="http://schemas.xmlsoap.org/ws/2005/04/discovery">
<d:Types xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery"
xmlns:dp0="http://www.onvif.org/ver10/network/wsdl">dp0:NetworkVideoTransmitter</d:Types>
</Probe>
</s:Body>
</s:Envelope>
It seems there some missing and extra parts.
Thanks in advance.
Original issue reported on code.google.com by [email protected]
on 15 Dec 2011 at 4:20
Unable to select the reply to address on systems with multiple networks cards
Original issue reported on code.google.com by [email protected]
on 27 Oct 2012 at 12:18
When using this piece of code:
WsDiscoveryServer wsd = WsDiscoveryFactory.createServer();
wsd.start();
WsDiscoveryService service1 = WsDiscoveryFactory.createService(
new QName("http://www.onvif.org/ver10/device/wsdl", "tds:Device"),
"onvif://www.onvif.org/name/AnalyticsUnit",
"http://192.168.20.130:8080/onvif/device_service");
wsd.publish(service1);
I have a discovery server running.
But when I receive "probe" messages with
"http://schemas.xmlsoap.org/ws/2005/04/discovery" namespace, the application
throws the following exception:
"com.ms.wsdiscovery.exception.WsDiscoveryXMLException: Unable to unmarshal SOAP
document"
...
unexpected element (uri:"http://schemas.xmlsoap.org/ws/2005/04/discovery",
local:"Probe").
...
expected elements are ...
<{http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01}Probe> ...
So how can I do in order to support both SOAPOverUDP11 & SOAPOverUDPDraft2004
at the same time for the same discovery service?
I'm not responsible of the webservice clients (could be thousand of different
devices on the market)
Thank you for your help
H. Terelle
Original issue reported on code.google.com by [email protected]
on 22 Mar 2012 at 4:08
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.