SyntaxHighlighter

Wednesday, October 7, 2015

jUDDI v3.3.1 release!

This release fixes a few bugs and introduces the jUDDI command line client. Enjoy!

Tuesday, August 4, 2015

jUDDI 3.3.0 Release

Today, we have released jUDDI version 3.3.0!  This version contains a number of bug fixes and offer's enhanced functionality in the user interface for interacting with tModels. Thirelease resolved a incredible 63 jiras. The release notes are accessible here: Release Notes

Here are some highlights for this version 3.3.0
  • Implementation of UDDIv3 Replication API and completed implementation of the Custody Transfer API
  • juddi-gui, numerous enhancements, service editor was redesigned to help make binding editing easier and simpler, more i18n work and security fixes
  • Nodes can change IDs
  • More administrative UI capabilities
  • A semi full featured command line jUDDI client (although it was missed in the release binaries)
You can grab the release at: 

Friday, December 5, 2014

jUDDI v3.2.1 Released

jUDDI Version 3.2.1 Released

Today we released jUDDI version 3.2.1! This version contains a number of bug fixes and offer's enhanced functionality in the user interface for interacting with tModels. This release resolved a incredible 65 jiras, as you can see in the Release Notes.

What new in version 3.2.1?

  • Numerous enhancements to juddi-gui (web user interface) including several security fixes, more internationalization support, 
  • More automated unit tests and refactoring
  • Database DDL files are now auto generated with each build
  • Fixes for the newer versions of Hibernate
  • We're now using GIT for cvs
You can grab the release here:

The website will be updated as soon as the ASF Infrastructure team get the CMS repo up and running again.

Thursday, February 6, 2014

UDDI: Universal Description, Discovery, and Integration

Check out the free chapter on UDDI of the O'Reilly 'Java WebService' book by Tyler Jewell
http://oreilly.com/catalog/javawebserv/chapter/ch06.html

It gives a very nice overview on how to use UDDI in general as well as some good detail on how to use taxonomies.

Cheers,

--Kurt

jUDDI 3.2.0 Released - Now with a full GUI!

jUDDI Version 3.2.0 Released

Today we released jUDDI version 3.2.0! This version marks the first jUDDI release with a full featured console. Suddenly jUDDI has become much easier to use. This release resolved a incredible 206(!) jiras, as you can see in the Release Notes.

What new in version 3.2?


  • A new end user interface based on Twitter’s Bootstrap
  • A new administrative user interface based on Twitter’s Bootstrap with in browser monitoring
  • A client side subscription callback API
  • Client distribution package
  • Many more examples
  • WADL to UDDI mappings
  • All credentials are now encryptable with command line tools
  • Removal of the portlet services
  • Deployment templates for JBoss EAP 6+
  • Client side digital signature support
  • REST style interface for Inquiry API
  • Added many more tModels to the base install
  • More documentation

Admin and jUDDI GUI Web based consoles

This is the first release that features a the juddi-gui. A screen capture of the juddi-gui Service Editor is shown in Figure 1. A demo cloud instance is running at http://uddiconsole-jbossoverlord.rhcloud.com if you want to try it out.

Figure 1. Screen capture of the juddi-gui Service Editor.
Figure 2 shows a the admin console as part of the juddiv3 server. The juddi-gui runs in the same servlet container but it can run remotely as well since it connects to the server over HTTP/S only.
Figure 2. High Level Application Diagram showing the jUDDI server as well as the admin console and juddi-gui.
Finally if we zoom into the juddiv3 application itself, see Figure 3, it shows the various deployment options jUDDI gives you in terms of container and database choice, JPA and JAXWS providers and connection protocols.


Figure 3. jUDDI architecture showing the plugable components.

Getting Started:

Either try out the demo cloud instance, simply download the distribution from http://juddi.apache.org/releases.html, and start the preconfigured tomcat with the UDDI server and GUI; all you have to do is unzip, start tomcat and in your browser navigate to http://localhost:8080/juddiv3.
  • Then follow the Getting Started Chapter of the jUDDI Guide.
  • Scripted support for deployment to other application servers such as JBoss EAP.
  • Detailed documentation guides and javadoc.
  • Code examples on how to interact with the UDDI server.

Documentation:

http://juddi.apache.org/docs/3.2/juddi-guide/html/
http://juddi.apache.org/docs/3.2/juddi-client-guide/html/

Cheers,

--Kurt




Apache jUDDI releases v3.2!

The Apache Software Foundation jUDDI project has just released version 3.2

This release covers over 200 tickets, has a brand new Bootstrap based user interface and is just simply light years of the previous one in terms of features, usability, test cases and documentation. Enjoy!

More details to be posted soon!

Saturday, January 4, 2014

Discovering the Discovery Service?

One of the problems that always bothered me with UDDI is that you need to know a number of things in order to find something. Specifically, you need

  1. The location of the UDDI services, at least the Inquiry
  2. Information about what you're looking for
  3. Optionally, credentials
So we need to know where UDDI is before we can look up the where the services are that we want to use? This is almost a catch 22 scenario. Consider a scenario where you have 1000s of web serivce clients, all depending on the UDDI server for figuring out how to route requests. What is the UDDI server location changes? Now you have a few angry IT guys to deal with.

Falling in line with most IT solutions of making things easier and reducing complexity, how do we remove the extra step of locating UDDI? There's a few options and they are all multicast based solutions.
The jUDDI team has had a number of discussions about this and have opened a ticket to enable one of these capabilities in the future, currently slated for version 3.3.

If you happen to have an opinion on the subject, please feel free to share.