You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by al...@calbazana.com on 2007/12/07 03:43:50 UTC
So... UDDI?
Hello,
Is anyone out there using a UDDI registry for their services? I'm
considering a registry for our loose bundling of web services, but we
only have a handful of services in play. I am not sure if a registry is
overkill given our setup.
I started looking at UDDI this afternoon when I got fed up with adding
wsdl (and related schema) to my BPEL partner link definitions. JDeveloper
offers the ability to point to a UDDI registry to "discover" wsdl for
partner links.
Thanks,
Alejandro
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: So... UDDI?
Posted by Martin Gainty <mg...@hotmail.com>.
Thanks Paul
Any chance we can see a sample deployment.xml?
Thanks again
Martin--
----- Original Message -----
From: Paul Fremantle
To: axis-user@ws.apache.org
Sent: Sunday, December 09, 2007 4:53 AM
Subject: Re: So... UDDI?
Dennis
We are working on documentation and architecture documents. However, if you want to look at some key architecture I can recommend two quick looks.
The first is the simple Registry interface which is the heart of the API ( e.g. if you want to embed this, use it as a client, or create your own backend).
https://wso2.org/repos/wso2/trunk/registry/modules/core/src/main/java/org/wso2/registry/Registry.java
And here is the definition of the REST interface to the registry:
http://wso2.org/wiki/display/registry/Registry+Protocol
Paul
On Dec 9, 2007 6:22 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
Hi Paul,
Great to see this! It's something that I've thought was needed for a
long time. UDDI was designed for a world that doesn't now exist, and is
unlikely to develop within our lifetimes, where AI-type applications are
able to analyze services based on simple descriptions and link them
together at runtime to fulfill user needs (via liberal application of
magic pixie dust). It's a shame that it was blessed as a Java standard
by the Sun process when it had so little in the way of useful
functionality, but I think that's just due to the political nature of
the standardization process.
It'll be great when WSO2 gets out some user documentation (or even
architecture documents) for the project. I'm personally not big on
looking through source code to deduce where a project is going, but I
heartily approve of the goals.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Paul Fremantle wrote:
> You might want to look at the project being built here - its about
> using lightweight REST models to build a registry instead of UDDI.
>
> http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
> < http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html>
>
> Paul
>
> On Dec 7, 2007 2:43 AM, <alejandro@calbazana.com
> <ma...@calbazana.com>> wrote:
>
> Hello,
>
> Is anyone out there using a UDDI registry for their services? I'm
> considering a registry for our loose bundling of web services,
> but we
> only have a handful of services in play. I am not sure if a
> registry is
> overkill given our setup.
>
> I started looking at UDDI this afternoon when I got fed up with adding
> wsdl (and related schema) to my BPEL partner link definitions.
> JDeveloper
> offers the ability to point to a UDDI registry to "discover" wsdl for
> partner links.
>
> Thanks,
>
> Alejandro
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <mailto:axis-user-help@ws.apache.org >
>
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@wso2.com <ma...@wso2.com>
>
> "Oxygenating the Web Service Platform", www.wso2.com
> <http://www.wso2.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: So... UDDI?
Posted by Paul Fremantle <pz...@gmail.com>.
Dennis
We are working on documentation and architecture documents. However, if you
want to look at some key architecture I can recommend two quick looks.
The first is the simple Registry interface which is the heart of the API (
e.g. if you want to embed this, use it as a client, or create your own
backend).
https://wso2.org/repos/wso2/trunk/registry/modules/core/src/main/java/org/wso2/registry/Registry.java
And here is the definition of the REST interface to the registry:
http://wso2.org/wiki/display/registry/Registry+Protocol
Paul
On Dec 9, 2007 6:22 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Hi Paul,
>
> Great to see this! It's something that I've thought was needed for a
> long time. UDDI was designed for a world that doesn't now exist, and is
> unlikely to develop within our lifetimes, where AI-type applications are
> able to analyze services based on simple descriptions and link them
> together at runtime to fulfill user needs (via liberal application of
> magic pixie dust). It's a shame that it was blessed as a Java standard
> by the Sun process when it had so little in the way of useful
> functionality, but I think that's just due to the political nature of
> the standardization process.
>
> It'll be great when WSO2 gets out some user documentation (or even
> architecture documents) for the project. I'm personally not big on
> looking through source code to deduce where a project is going, but I
> heartily approve of the goals.
>
> - Dennis
>
> --
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Axis2 Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
> Paul Fremantle wrote:
> > You might want to look at the project being built here - its about
> > using lightweight REST models to build a registry instead of UDDI.
> >
> > http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
> > <http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html>
> >
> > Paul
> >
> > On Dec 7, 2007 2:43 AM, <alejandro@calbazana.com
> > <ma...@calbazana.com>> wrote:
> >
> > Hello,
> >
> > Is anyone out there using a UDDI registry for their services? I'm
> > considering a registry for our loose bundling of web services,
> > but we
> > only have a handful of services in play. I am not sure if a
> > registry is
> > overkill given our setup.
> >
> > I started looking at UDDI this afternoon when I got fed up with
> adding
> > wsdl (and related schema) to my BPEL partner link definitions.
> > JDeveloper
> > offers the ability to point to a UDDI registry to "discover" wsdl
> for
> > partner links.
> >
> > Thanks,
> >
> > Alejandro
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
> >
> >
> > --
> > Paul Fremantle
> > Co-Founder and VP of Technical Sales, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > blog: http://pzf.fremantle.org
> > paul@wso2.com <ma...@wso2.com>
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> > <http://www.wso2.com>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: So... UDDI?
Posted by Anne Thomas Manes <at...@gmail.com>.
Dennis,
I agree that the original design concept for UDDI -- a single global
registry of services that would enable dynamic discovery of business
partners -- was just a bit far fetched. In fact, the idea of using
UDDI as the primary means of service discovery within an organization
is a bit far fetched. But UDDI does play a very important role in a
SOA runtime infrastructure, which is an ecosystem of cooperating
products (service platforms, mediation systems, and management
systems) that need a way to exchange information about services. UDDI
is not perfect, and I'd like to see someone propose additional APIs to
augment SOAP, but it does provide a standard system of record for the
environment and a standard means to retrieve information about
service.
As I said, UDDI makes an incredibly poor repository to support
development time discovery and governance. It simply doesn't contain
enough information about services and service artifacts, and the data
model organization is just wrong to support development activities. (I
will note, though, that all IDEs have a built-in UDDI browsing
capability.) I recommend using a repository to support development
time activities, and maintain the registry to support the runtime
system of record capability.
Note that the leading registry/repository vendors (HP/Systinet,
Software AG/Infravio, BEA, and IBM) have either extended UDDI with
repository features (Software AG) or they offer a separate repository
that synchronizes with the UDDI registry (the others).
The HP/Systinet repository sounds somewhat similar to Paul's project.
It is an entirely REST-based repository. I find it interesting that
Systinet found it necessary to define a Java API to abstract the REST
API to make it more palatable to the average enterprise developer.
(Paul -- I suggest you confer with Radovan on your API.)
Anne
On Dec 8, 2007 11:22 PM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Hi Paul,
>
> Great to see this! It's something that I've thought was needed for a
> long time. UDDI was designed for a world that doesn't now exist, and is
> unlikely to develop within our lifetimes, where AI-type applications are
> able to analyze services based on simple descriptions and link them
> together at runtime to fulfill user needs (via liberal application of
> magic pixie dust). It's a shame that it was blessed as a Java standard
> by the Sun process when it had so little in the way of useful
> functionality, but I think that's just due to the political nature of
> the standardization process.
>
> It'll be great when WSO2 gets out some user documentation (or even
> architecture documents) for the project. I'm personally not big on
> looking through source code to deduce where a project is going, but I
> heartily approve of the goals.
>
> - Dennis
>
> --
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Axis2 Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
> Paul Fremantle wrote:
> > You might want to look at the project being built here - its about
> > using lightweight REST models to build a registry instead of UDDI.
> >
> > http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
> > <http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html>
> >
> > Paul
> >
> > On Dec 7, 2007 2:43 AM, <alejandro@calbazana.com
> > <ma...@calbazana.com>> wrote:
> >
> > Hello,
> >
> > Is anyone out there using a UDDI registry for their services? I'm
> > considering a registry for our loose bundling of web services,
> > but we
> > only have a handful of services in play. I am not sure if a
> > registry is
> > overkill given our setup.
> >
> > I started looking at UDDI this afternoon when I got fed up with adding
> > wsdl (and related schema) to my BPEL partner link definitions.
> > JDeveloper
> > offers the ability to point to a UDDI registry to "discover" wsdl for
> > partner links.
> >
> > Thanks,
> >
> > Alejandro
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
> >
> >
> > --
> > Paul Fremantle
> > Co-Founder and VP of Technical Sales, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > blog: http://pzf.fremantle.org
> > paul@wso2.com <ma...@wso2.com>
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> > <http://www.wso2.com>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: So... UDDI?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Hi Paul,
Great to see this! It's something that I've thought was needed for a
long time. UDDI was designed for a world that doesn't now exist, and is
unlikely to develop within our lifetimes, where AI-type applications are
able to analyze services based on simple descriptions and link them
together at runtime to fulfill user needs (via liberal application of
magic pixie dust). It's a shame that it was blessed as a Java standard
by the Sun process when it had so little in the way of useful
functionality, but I think that's just due to the political nature of
the standardization process.
It'll be great when WSO2 gets out some user documentation (or even
architecture documents) for the project. I'm personally not big on
looking through source code to deduce where a project is going, but I
heartily approve of the goals.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Paul Fremantle wrote:
> You might want to look at the project being built here - its about
> using lightweight REST models to build a registry instead of UDDI.
>
> http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
> <http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html>
>
> Paul
>
> On Dec 7, 2007 2:43 AM, <alejandro@calbazana.com
> <ma...@calbazana.com>> wrote:
>
> Hello,
>
> Is anyone out there using a UDDI registry for their services? I'm
> considering a registry for our loose bundling of web services,
> but we
> only have a handful of services in play. I am not sure if a
> registry is
> overkill given our setup.
>
> I started looking at UDDI this afternoon when I got fed up with adding
> wsdl (and related schema) to my BPEL partner link definitions.
> JDeveloper
> offers the ability to point to a UDDI registry to "discover" wsdl for
> partner links.
>
> Thanks,
>
> Alejandro
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@wso2.com <ma...@wso2.com>
>
> "Oxygenating the Web Service Platform", www.wso2.com
> <http://www.wso2.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: So... UDDI?
Posted by "Johnson, David E" <da...@intel.com>.
Have you thought of Open SCA and managing application control that way?
David E.A. Johnson
Director, Digital Security Products
Intel Corporation
SSG-ESSD
1815 S. Meyers Rd., Suite 150
Oakbrook Terrace, Illinois 60441
770-433-3272 direct
404-769-7207 mobile
________________________________
From: Paul Fremantle [mailto:pzfreo@gmail.com]
Sent: Thursday, December 06, 2007 9:50 PM
To: axis-user@ws.apache.org
Subject: Re: So... UDDI?
You might want to look at the project being built here - its about using
lightweight REST models to build a registry instead of UDDI.
http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
Paul
On Dec 7, 2007 2:43 AM, <al...@calbazana.com> wrote:
Hello,
Is anyone out there using a UDDI registry for their services? I'm
considering a registry for our loose bundling of web services, but we
only have a handful of services in play. I am not sure if a registry is
overkill given our setup.
I started looking at UDDI this afternoon when I got fed up with adding
wsdl (and related schema) to my BPEL partner link definitions.
JDeveloper
offers the ability to point to a UDDI registry to "discover" wsdl for
partner links.
Thanks,
Alejandro
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: So... UDDI?
Posted by Paul Fremantle <pz...@gmail.com>.
You might want to look at the project being built here - its about using
lightweight REST models to build a registry instead of UDDI.
http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html
Paul
On Dec 7, 2007 2:43 AM, <al...@calbazana.com> wrote:
> Hello,
>
> Is anyone out there using a UDDI registry for their services? I'm
> considering a registry for our loose bundling of web services, but we
> only have a handful of services in play. I am not sure if a registry is
> overkill given our setup.
>
> I started looking at UDDI this afternoon when I got fed up with adding
> wsdl (and related schema) to my BPEL partner link definitions. JDeveloper
> offers the ability to point to a UDDI registry to "discover" wsdl for
> partner links.
>
> Thanks,
>
> Alejandro
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com