Web service discovery in WCF : Ws-Discovery or UDDI?

Question

I know the distinction between UDDI and Ws-Discovery (well know location to search a service vs broadcast). But my question is : what is the simplest way to discover a webservic

Answer 1

jUDDI has a .NET client that you can use. It greatly simplifies a number of things for working with UDDI.

From experience, there's there only two or three functioning implementations of WS-Discovery.

• Apache CXF, but only when ran outside of a container
• This one: https://code.google.com/p/java-ws-discovery/ which doesn't work in Jboss and is unmaintained
• Microsoft .NET 4.0ish

UDDI you can access from anything. There are many client and server implementations. (Just the version 3 stuff is listed here)

• IBM WS-Registry
• Apache jUDDI
• Microsoft UDDI v3 with Biztalk (its free with 2008 server)
• HP SOA/Systinet or whatever it's called now
• WSO2 has something
• ebXML has some kind of bridge or adapter

There's even a REST endpoint for UDDI3 (jUDDI 3.2 has it, XML or JSON responses) which opens this up to many more possibilities.

In addition, the data that's sharable with WS-Discovery is somewhat limited compared to the virtually unlimited data you can attach to UDDI.

That's just my 2 cents.