Thanks Paul

Any chance we can see a sample deployment.xml?

Thanks again
Martin--
  ----- Original Message ----- 
  From: Paul Fremantle 
  To: [email protected] 
  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 <[EMAIL PROTECTED]> 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, <[EMAIL PROTECTED]

    > <mailto:[EMAIL PROTECTED]>> 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: [EMAIL PROTECTED]

    >     <mailto:[EMAIL PROTECTED]>

    >     For additional commands, e-mail: [EMAIL PROTECTED]

    >     <mailto:[EMAIL PROTECTED] >

    >
    >
    >
    >
    > --
    > Paul Fremantle
    > Co-Founder and VP of Technical Sales, WSO2
    > OASIS WS-RX TC Co-chair
    >
    > blog: http://pzf.fremantle.org

    > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>

    >
    > "Oxygenating the Web Service Platform", www.wso2.com

    > <http://www.wso2.com>



    --------------------------------------------------------------------- 
    To unsubscribe, e-mail: [EMAIL PROTECTED]
    For additional commands, e-mail: [EMAIL PROTECTED] 





  -- 
  Paul Fremantle
  Co-Founder and VP of Technical Sales, WSO2
  OASIS WS-RX TC Co-chair

  blog: http://pzf.fremantle.org 
  [EMAIL PROTECTED]

  "Oxygenating the Web Service Platform", www.wso2.com 

Reply via email to